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

Clone this repo:
  1. 679bd52 recovery: use portable printf by Mike Frysinger · 5 weeks ago factory-coral-10122.B factory-fizz-10167.B firmware-fizz-10139.B master release-R64-10176.B
  2. e895698 recovery: use /run directly by Mike Frysinger · 7 weeks ago firmware-coral-10068.B
  3. dda4967 recovery: process SUCCESS_COLD_REBOOT from tpm fw updater by Andrey Pronin · 8 weeks ago
  4. 9bd6f53 Revert "recovery: Use the static linked version of futility" by Douglas Anderson · 9 weeks ago firmware-scribe-10045.B
  5. 436366c recovery: Use the static linked version of futility by Douglas Anderson · 9 weeks ago

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.