| commit | 8cbe8d4d9392243aab7e64c51d5d725574d6cf5c | [log] [tgz] |
|---|---|---|
| author | Alexis Savery <asavery@chromium.org> | Tue Jan 24 03:27:00 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Jan 26 06:12:33 2017 |
| tree | 7bd75a5ce3f4fa67da89c34227eb003b78ea85dc | |
| parent | af9eb2d5bff8f25f7dc3234b1086fb5d9952ec44 [diff] |
recovery: Replace hardcoded device-mapper major Replace hardcoded device-mapper major to account for the new device driver NVMe, which is now the block device driver with major 254. BUG=chromium:676692 TEST=Recovery logs show the device mapper successfully configured. Change-Id: Ifc4d42c59c28587057cfbf86a0969c9b17977c5e Reviewed-on: https://chromium-review.googlesource.com/431580 Commit-Ready: Alexis Savery <asavery@chromium.org> Tested-by: Alexis Savery <asavery@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-by: Mike Frysinger <vapier@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.