| commit | a0f0b6ba3da4e4bcf9ffd277e903b19c75501fca | [log] [tgz] |
|---|---|---|
| author | Shelley Chen <shchen@chromium.org> | Fri Feb 03 18:57:38 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Mar 03 04:17:44 2017 |
| tree | 1ee7e09465ad7a02f3a2cff04836f07b75641431 | |
| parent | 8cbe8d4d9392243aab7e64c51d5d725574d6cf5c [diff] |
Recovery: Adding FW rollback check BUG=chromium:652748 BRANCH=None TEST=build recovery image and ran it on chell & sentry. Change-Id: I3e07dd76adfe98b92e2c53daf3b8b5866cf1cd62 Signed-off-by: Shelley Chen <shchen@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/437592 Reviewed-by: Randall Spangler <rspangler@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.