Firstly kudos for your excellent work so far.
I'd like to understand how booting works, after one has followed your instructions. Am I right that:
- The default "verified" uboot bootloader is not used (nor is the alternate "non-verified" nv-uboot bootloader? For more details on nv-uboot, please see "Appendix A: Using nv-U-Boot on the Samsung ARM Chromebook":
http://www.chromium....-arm-chromebook ). It seems you somehow use "firmware-linux" and "firmware-libertas" instead. I've never heard of those (as I'm only familiar with how GRUB works, on PC's). What are those? What do they do?
- "firmware-linux" and "firmware-libertas" somehow boots a "stock" linux kernel that you compiled and packaged yourself, called "linux-image-exynos5" (as opposed to "borrowing" and "signing" the ChromeOS kernel, which is what one must unfortunately do using the current instructions found on "InstallingDebianOn Samsung ARMChromebook":
- When future versions of your "linux-image-exynos5" are released (say, because there was an important security update released for the kernel), they'll "just work" (at boot time), when one installs them with "sudo apt-get update && sudo apt-get upgrade"?
If I'm correct on these 3 points, then how were you able to "get away with" not using the nv-uboot bootloader? That is to say, why couldn't the Debian folks follow suit and boot their own stock linux kernels with "firmware-linux" and "firmware-libertas" like you do?
Note: The Debian folks are currently stuck on how to boot a stock linux kernel from nv-u-boot, as seen on
"InstallingDebianOn Samsung ARMChromebook":
"Three partitions are created on the disk. In time, the intention is that these be used for:
- a copy of nv-uboot that is chainloaded by the standard firmware,
- a /boot filesystem containing the standard (non-ChromeOS) kernel, read by nv-uboot,
- the root filesystem.
Currently nv-uboot is *not* used, and so the arrangement is:
- a copy of the ChromeOS kernel that is loaded by the standard firmware,
- a /boot filesystem that is used only to contain the ChromeOS kernel (which is not used during booting, just during the preparation of the previous partition),
- the root filesystem."
I would appreciate any clarification, as you seem to understand these things really well. GPT and "verified" bootloaders are tough to understand, especially when it comes to how to boot stock linux kernels.