| commit | b85c6992c6e3b182fa9d632587332999e9ec25a5 | [log] [tgz] |
|---|---|---|
| author | Hung-Te Lin <hungte@chromium.org> | Wed May 10 04:48:30 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Wed May 10 14:08:28 2017 |
| tree | 492e8b2dd0d14ef5035e2d99a70050e95a4e1522 | |
| parent | 363f58be64023da920f1aaac40fc552f8a46107f [diff] |
factory_netboot: Add cros_payload and new factory_installer files. The factory installer has been updated with new factory_* scripts and using cros_payload (need jq, curl), so we do want to include them in netboot shim. BUG=chromium:711615 TEST=./make_netboot.sh --board eve Change-Id: I7f9c0f75598b9d76126d67c259e6658eb44f13eb Reviewed-on: https://chromium-review.googlesource.com/501687 Commit-Ready: Hung-Te Lin <hungte@chromium.org> Tested-by: Hung-Te Lin <hungte@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.