Various initramfs images for Chrome OS: recovery, factory, etc...

Clone this repo:
  1. 99ffe3b recovery: Adjust TPM firmware updating decision by Mattias Nissler · 7 days ago master
  2. c2da8e4 recovery: Store firmware log during recovery by Julius Werner · 11 days ago
  3. a5a7579 factory_shim: disable jobs arc-oemcrypto, swap, and syslog. by You-Cheng Syu · 7 weeks ago firmware-scarlet-10388.B release-R65-10323.B stabilize-10323.29.B
  4. a8612aa factory_shim: factory_shim: Remove block_devmode check from bootstrap.sh by Sam Hurst · 2 months ago
  5. 679bd52 recovery: use portable printf by Mike Frysinger · 4 months ago firmware-fizz-10139.94.B firmware-fizz-10139.B release-R64-10176.B stabilize-10176.13.B stabilize-10176.47.B stabilize-10176.54.B stabilize-10176.58.B stabilize-10176.65.B

Chromium OS initramfs

Build logic for creating standalone initramfs environments.

See the README files in the respective subdirs for more details.

To Use

Normally you wouldn't build in this directory directly. Instead, you would build the chromeos-initramfs package with the right USE flags. e.g.:

$ USE=recovery_ramfs emerge-$BOARD chromeos-initramfs

That will install the cpio initramfs files into the sysroot for you to build into a kernel directly. The various build scripts would then be used to make the right kernel/image using those (e.g. mod_image_for_recovery.sh).

To Make

You could build these by hand for quick testing. Inside the chroot:

$ make SYSROOT=/build/$BOARD BOARD=$BOARD <target>

That will create the cpio archives for you.