Google Git
Sign in
chromium / chromiumos / platform / initramfs / 0dd7920c119896ddfac9f9f73518a1befa6c0c4a
commit0dd7920c119896ddfac9f9f73518a1befa6c0c4a[log] [tgz]
authorTing Shen <phoenixshen@google.com>Fri Jun 05 07:41:18 2020
committerCommit Bot <commit-bot@chromium.org>Fri Jun 05 09:36:17 2020
tree6a3cdcee1735490c840bce9e0e153f350c829d8a
parent89b98139a1820ad198176fba92f39c4e6f5bc6e5 [diff]
menu_ui: fix make script failure

Since there's no png files in assets dir now, `cp assets/*.png some_dir`
will fail. Remove that command.

BUG=None
TEST=USE="menu_ui recovery_ramfs" make chromeos-initramfs

Change-Id: I81c600a899fe8ae8d71047af04d5431345dd7cd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2231869
Reviewed-by: Joel Kitching <kitching@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Tested-by: Ting Shen <phoenixshen@chromium.org>
Commit-Queue: Ting Shen <phoenixshen@chromium.org>
1 file changed
tree: 6a3cdcee1735490c840bce9e0e153f350c829d8a
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. hypervisor/
  5. recovery/
  6. test/
  7. .gitignore
  8. LICENSE
  9. Makefile
  10. OWNERS
  11. README.md
README.md

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:

  1. mount -o remount,exec /mnt/stateful_partition
  2. mkdir /mnt/stateful_partition/test; cd /mnt/stateful_partition/test
  3. xzcat /tmp/XXXXXX_ramfs.cpio.xz | cpio -iv
  4. stop ui; kill $(pidof frecon)
  5. bind mount /dev, /proc, /sys and /tmp in /mnt/stateful_partition/test
  6. chroot /mnt/stateful_partition/test/init
  7. Iterate.