Re: [RFC v2 3/7] firmware: port built-in section to linker table

From: Kees Cook
Date: Tue May 03 2016 - 13:21:45 EST

On Tue, May 3, 2016 at 10:10 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxxx> wrote:
> On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez <mcgrof@xxxxxxxx> wrote:
>> Thanks! Can you confirm if any Android or Brillo builds are already using it?
> Also more importantly, any chance you can provide any technical
> reasons why initramfs cannot be used, or it was decided to not use it
> on these systems? It should help others in the future as well.

In Chrome OS, the kernels are built specifically for the hardware
they're going to be on, so an initramfs was seen as a needless
additional boot step. Since Chrome OS was heavily optimized for boot
speed, it was designed to not need the initramfs at all. This is
actually enforced by the read-only boot firmware, so there's no
trivial way to _start_ using an initramfs on (existing) Chrome OS
devices either.


Kees Cook
Chrome OS & Brillo Security