Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / platform / initramfs / 6738184c18ed72c5278020cc4ada1da4fc46218a
commit6738184c18ed72c5278020cc4ada1da4fc46218a[log] [tgz]
authorJae Hoon Kim <kimjae@chromium.org>Thu Apr 29 19:26:43 2021 -0700
committerCommit Bot <commit-bot@chromium.org>Tue May 04 21:32:49 2021 +0000
treef2da1c028830888a26e429c32dcd2f828f9038ed
parent2ee9f228e5f6d34a2a0801c3d1c69285628e4187 [diff]
initramfs: Add `log_area_border_large.svg`

Create a larger log area png to fit more char in a line for when viewing
logs from the UI.

BUG=b:186569605
TEST=# build initramfs + see generated png.

Change-Id: Ied6e57669b62de431b96221497d65f3069f7971a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2861970
Tested-by: Jae Hoon Kim <kimjae@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Amin Hassani <ahassani@chromium.org>
Commit-Queue: Jae Hoon Kim <kimjae@chromium.org>
1 file changed
tree: f2da1c028830888a26e429c32dcd2f828f9038ed
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. hypervisor/
  5. minios/
  6. recovery/
  7. test/
  8. .gitignore
  9. LICENSE
  10. Makefile
  11. OWNERS
  12. 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 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.