| commit | 679bd52ef414fdcd1b9a01081498a66eb1388c81 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Mon Oct 23 19:59:55 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sat Nov 04 20:27:00 2017 |
| tree | 5d2af2b308bc09e1aa7d7f2b998ca82b436fa44a | |
| parent | e895698b7005bbbd518b93b5d303d347c8f2ed1f [diff] |
recovery: use portable printf The echo command does not reliably support -e/-n flags. BUG=None TEST=samus recovery kernel still works Change-Id: Ia3543c0f535448f48746ee1fb90382e03d35d396 Reviewed-on: https://chromium-review.googlesource.com/738552 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Hung-Te Lin <hungte@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.