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

Clone this repo:
  1. a0f0b6b Recovery: Adding FW rollback check by Shelley Chen · 3 weeks ago master release-R58-9334.B
  2. 8cbe8d4 recovery: Replace hardcoded device-mapper major by Alexis Savery · 8 weeks ago firmware-cr50-9308.B stabilize-9313.B
  3. af9eb2d factory_netboot: Use kmod for modprobe with all dependency files. by Hung-Te Lin · 3 months ago stabilize-9157.B stabilize-9199.B stabilize-9202.B stabilize-fsi-9202.5.0.B
  4. 5b9b3a3 factory_netboot: Add modprobe into bin dependency. by Hung-Te Lin · 4 months ago firmware-reef-9042.B firmware-servo-9040.B stabilize-9093.B
  5. 43b239f test: Improve usage guide and qemu testing experience. by Hung-Te Lin · 4 months 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.