Google Git
Sign in
chromium / chromiumos / platform / initramfs / refs/heads/firmware-volteer-13521.B
commita015b71599dbd74dd2f6b0cdc39d5507be1cf504[log] [tgz]
authorTomasz Jeznach <tjeznach@chromium.org>Thu Oct 08 03:51:55 2020
committerCommit Bot <commit-bot@chromium.org>Thu Oct 08 19:24:39 2020
tree79f1c809ef6c178ccf7f1e277c02191549b65dd9
parent6fea142675ee2f345a226c382ef3b41245689e3a [diff]
hypervisor: fix PCI ID skip list.

Fix incorrect PCI ID skip list for eve device.

BUG=None
TEST=build & boot eve.

Change-Id: I2d2e035ee074cdea83ea679819b246d94e85e55f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2459492
Tested-by: Tomasz Jeznach <tjeznach@chromium.org>
Auto-Submit: Tomasz Jeznach <tjeznach@chromium.org>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
1 file changed
tree: 79f1c809ef6c178ccf7f1e277c02191549b65dd9
  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 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.