Google Git
Sign in
chromium / chromiumos / platform / initramfs / refs/heads/firmware-octopus-11297.B
commit9cf462923fbfa414101d05ca62e45bd1f58cf4c1[log] [tgz]
authorMike Frysinger <vapier@chromium.org>Tue Nov 06 03:56:08 2018
committerchrome-bot <chrome-bot@chromium.org>Wed Nov 07 14:35:01 2018
tree07f91d5df51e68eae13ceb697b429a36de6d9fe8
parentbfd6bd868d07f30fa6696eaf4587c22333a027ab [diff]
make_images: support fallback English translations ourselves

Grit has changed behavior where it won't write out the fallback
English translations to the non-English messages.  That means we
have to write out the English database ourselves, and then load
the missing content from it on the fly.

This makes it easy to issue warnings when translations are missing.

BUG=chromium:757792
TEST=generating screens with new & old grit are the same

Change-Id: I4061d04377c18ba6d9eb7946591a6a9728d4f314
Reviewed-on: https://chromium-review.googlesource.com/1319409
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Amin Hassani <ahassani@chromium.org>
2 files changed
tree: 07f91d5df51e68eae13ceb697b429a36de6d9fe8
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. recovery/
  5. test/
  6. .gitignore
  7. LICENSE
  8. Makefile
  9. OWNERS
  10. 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.