Repository navigation
intel platforms: add list of Chromebook dev. environments - #379
Conversation
| 4. Chromebooks and SOF | ||
| ---------------------- | ||
|
|
||
| As stated above, Chromebook firmware is as of 2021 configured with the |
There was a problem hiding this comment.
this is more circa 2019/2020
There was a problem hiding this comment.
I meant "up to today 2021". As a native speaker could you help me rephrase?
There was a problem hiding this comment.
Ah if you meaning as "at the time of writing this" then I think this is good. We have 0 intent to change this, so I think its safe to write it as a "beginning in" style fashion to convey when the switch happened
| As stated above, Chromebook firmware is as of 2021 configured with the | ||
| *community* key which means Chromebooks can run audio firmware signed by | ||
| anyone. The entire filesystem is locked by default instead but there are | ||
| a couple options to disable security for development purposes. |
There was a problem hiding this comment.
recommend linking to dev mode process? https://chromium.googlesource.com/chromiumos/docs/+/master/developer_mode.md
There was a problem hiding this comment.
You're right, I didn't because I assume the developer guide below already would but the Developer Mode is of more general interest, not just for ChromeOS
There was a problem hiding this comment.
The link below is a few generations behind, this should always be up to date :)
| - ChromeOS has direct hardware access but development cannot happen on | ||
| ChromeOS itself, it requires a separate workstation similar to how | ||
| most embedded development does. Setting up its ``cros_sdk`` requires | ||
| significant time and effort, see the `ChromeOS developer guide |
There was a problem hiding this comment.
time yes, but it is "supposed" to be low effort... that being said, you do not need the cros_sdk to do strictly FW dev, if you want to modify the kernel then yes
There was a problem hiding this comment.
Good point about the kernel, thanks. I tried to avoid making a difference between SOF fw and the kernel (similar problem with Crouton) to keep this section short but now I think it's too much of a shortcut.
| <https://docs.zephyrproject.org/2.7.0/boards/xtensa/intel_adsp_cavs25/doc/index.html>`_ | ||
| on how to use Crouton for SOF. | ||
|
|
||
| - Finally, it is possible to "dual-boot" a regular Linux distribution on |
There was a problem hiding this comment.
or just wipe it entirely?
There was a problem hiding this comment.
Good point, will add.
There was a problem hiding this comment.
"Dual-boot" is possible on some chromebooks? I rather more interested in this part. :) I'd like to know which ones support dual-boots.
And why it is least secure option?
There was a problem hiding this comment.
Yes, it is, I have coworkers how have done it. I believe you have to use grub or something of the sorts to pick your boot partition. I believe its least secure because it completely disables all boot verification, this might be different though with our latest version of depthcharge, Havent seen it done in a few years.
There was a problem hiding this comment.
"Dual-boot" is possible on some chromebooks?
chrx.org does that.
marc-hb
left a comment
There was a problem hiding this comment.
Thanks @cujomalainey for the thorough review!
| <https://docs.zephyrproject.org/2.7.0/boards/xtensa/intel_adsp_cavs25/doc/index.html>`_ | ||
| on how to use Crouton for SOF. | ||
|
|
||
| - Finally, it is possible to "dual-boot" a regular Linux distribution on |
There was a problem hiding this comment.
Good point, will add.
| - ChromeOS has direct hardware access but development cannot happen on | ||
| ChromeOS itself, it requires a separate workstation similar to how | ||
| most embedded development does. Setting up its ``cros_sdk`` requires | ||
| significant time and effort, see the `ChromeOS developer guide |
There was a problem hiding this comment.
Good point about the kernel, thanks. I tried to avoid making a difference between SOF fw and the kernel (similar problem with Crouton) to keep this section short but now I think it's too much of a shortcut.
| 4. Chromebooks and SOF | ||
| ---------------------- | ||
|
|
||
| As stated above, Chromebook firmware is as of 2021 configured with the |
There was a problem hiding this comment.
I meant "up to today 2021". As a native speaker could you help me rephrase?
| As stated above, Chromebook firmware is as of 2021 configured with the | ||
| *community* key which means Chromebooks can run audio firmware signed by | ||
| anyone. The entire filesystem is locked by default instead but there are | ||
| a couple options to disable security for development purposes. |
There was a problem hiding this comment.
You're right, I didn't because I assume the developer guide below already would but the Developer Mode is of more general interest, not just for ChromeOS
fredoh9
left a comment
There was a problem hiding this comment.
Overall looks good. Great to see the link to Zephyr document
| <https://docs.zephyrproject.org/2.7.0/boards/xtensa/intel_adsp_cavs25/doc/index.html>`_ | ||
| on how to use Crouton for SOF. | ||
|
|
||
| - Finally, it is possible to "dual-boot" a regular Linux distribution on |
There was a problem hiding this comment.
"Dual-boot" is possible on some chromebooks? I rather more interested in this part. :) I'd like to know which ones support dual-boots.
And why it is least secure option?
1c8e8b8 to
5996428
Compare
cujomalainey
left a comment
There was a problem hiding this comment.
couple nits but otherwise good
| ChromeOS by a regular Linux distribution on *some* Chromebooks and | ||
| forget it is a Chromebook entirely. This comes at a price however: it | ||
| is the least secure option and the more likely to make your device | ||
| permanently unusable ("brick"). That level of risk is highly dependent |
There was a problem hiding this comment.
Minus using a debuging tool
There was a problem hiding this comment.
Good point but I'm trying to keep this (most dangerous) section short and "simply scary" and debug tools would IMHO stray a bit too far from SOF. I believe there are enough references in case anyone wants to go and dive into serious Chromebook hacking.
I'm guessing you're thinking about https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging.md and similar? From past experience these solutions also tend to be somewhat model-dependent.
There was a problem hiding this comment.
From what I understand CCD should be supported going forward, its not the fastest thing in the world but if you want to unlock your system its better than opening some of these super thin cases.
There was a problem hiding this comment.
but yes i agree, good to make is scary :)
Add list of options to develop on Chromebooks and links - especially Zephyr's detailed Crouton guide. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
5996428 to
08fb806
Compare
| <https://docs.zephyrproject.org/2.7.0/boards/xtensa/intel_adsp_cavs25/doc/index.html>`_ | ||
| on how to use Crouton for SOF. | ||
|
|
||
| - Finally, it is possible to "dual-boot" a regular Linux distribution on |
There was a problem hiding this comment.
"Dual-boot" is possible on some chromebooks?
chrx.org does that.
| ChromeOS by a regular Linux distribution on *some* Chromebooks and | ||
| forget it is a Chromebook entirely. This comes at a price however: it | ||
| is the least secure option and the more likely to make your device | ||
| permanently unusable ("brick"). That level of risk is highly dependent |
There was a problem hiding this comment.
Good point but I'm trying to keep this (most dangerous) section short and "simply scary" and debug tools would IMHO stray a bit too far from SOF. I believe there are enough references in case anyone wants to go and dive into serious Chromebook hacking.
I'm guessing you're thinking about https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging.md and similar? From past experience these solutions also tend to be somewhat model-dependent.
|
@anton-intel @deb-intel shall we merge and fix grammar incrementally ? |
@lgirdwood Yes, please. I'll make some edits in a new pull request. |
Add list of options to develop on Chromebooks and links - especially
Zephyr's detailed Crouton guide.
Signed-off-by: Marc Herbert marc.herbert@intel.com