commit | 9cb1c512838b3513f4b0bcf02f31f05018cf77a0 | [log] [tgz] |
---|---|---|
author | Drew Davenport <ddavenport@chromium.org> | Fri May 12 17:13:27 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue May 16 20:37:03 2017 |
tree | faac60101a8502f551660346d1adc3dfad048d50 | |
parent | a878c6922db5fc5c2565b4058f1f4713ee5115aa [diff] |
initramfs: Remove ply-image references. Some recovery scripts contain "if frecon exists, run it; otherwise run ply-image" conditionals. We don't use X now, and frecon should always be available in non-headless builds, so run frecon unconditionally. BUG=chromium:691762 TEST=built and installed recovery image on device Change-Id: Icc192c7f525c5ad979a737bb4dffe1c27368e456 Reviewed-on: https://chromium-review.googlesource.com/505127 Commit-Ready: Drew Davenport <ddavenport@chromium.org> Tested-by: Drew Davenport <ddavenport@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org>
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.