commit | 4510af8444a752854acf64a1ad08f086ae60fb4e | [log] [tgz] |
---|---|---|
author | Hung-Te Lin <hungte@chromium.org> | Tue May 23 01:45:43 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue May 23 07:15:10 2017 |
tree | 6a3c5cf234fe49b32929c6045fa4137739b88e32 | |
parent | 9cb1c512838b3513f4b0bcf02f31f05018cf77a0 [diff] |
factory_shim: Prevent running boot-splash.conf To make normal boot path cleaner and faster, we want to remove 'factory' logic from boot-splash, so we have to patch it here to a dummy job to prevent being blocked by 'frecon' invocation. BUG=chromium:725086 TEST=build_image factory_install; Boots new install shim. Change-Id: I78c5c544d54296c7caf6be14a91c53705ef5da2f Reviewed-on: https://chromium-review.googlesource.com/511922 Commit-Ready: Hung-Te Lin <hungte@chromium.org> Tested-by: Hung-Te Lin <hungte@chromium.org> Reviewed-by: Youcheng Syu <youcheng@google.com>
Build logic for creating standalone initramfs environments.
See the README files in the respective subdirs for more details.
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).
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.