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

Clone this repo:
  1. 24782ca hypervisor: Add first unit test for init. by Junichi Uekawa · 5 days ago main
  2. 274648e hypervisor: Add mpstat. by Junichi Uekawa · 5 days ago
  3. 91d5334 hypervisor: use while loop. by Junichi Uekawa · 5 days ago
  4. ca36828 hypervisor: specify pcie MMCONFIG base and length by Xiong Zhang · 7 days ago
  5. 92111a9 hypervisor: Simplify vvu-proxy-device path generation code. by Junichi Uekawa · 7 days 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.

To Debug

It is possible to debug few of the initramfs targets in QEMU. Read test/README.md for more information.

Also, here is a shortcut for developing/debugging graphical bits in initramfs, without having to create a full image for every iteration.

After emerge-$BOARD, find your initramfs package from chroot /build/$BOARD/var/lib/initramfs and copy to a running DUT, for example /tmp/recovery_ramfs.cpio.xz, then do followings on DUT over SSH:

  1. mkdir /usr/local/test/; cd /usr/local/test
  2. xzcat /tmp/XXXXXX_ramfs.cpio.xz | toybox cpio -iv
  3. stop ui; kill $(pidof frecon)
  4. bind mount /dev, /proc, /sys and /tmp in /usr/local/test:
for d in dev proc sys tmp; do
   mount --bind /${d} /usr/local/test/${d}
done
  1. chroot /usr/local/test /init
  2. Iterate.