| commit | af9eb2d5bff8f25f7dc3234b1086fb5d9952ec44 | [log] [tgz] |
|---|---|---|
| author | Hung-Te Lin <hungte@chromium.org> | Tue Dec 27 02:43:26 2016 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Dec 27 10:43:05 2016 |
| tree | c58343a49e974b22235118a307f237e2c0d8ef84 | |
| parent | 5b9b3a35dbd91dbd3b2ceb7e20656016e416fa62 [diff] |
factory_netboot: Use kmod for modprobe with all dependency files. Current modprobe is based on kmod and needs dependency files in /lib/modules/*/modules.*. To support loading USB ethernet dongles, we should fix the module loading path by providing required files. BUG=chromium:672751,chrome-os-partner:61315 TEST=Manually verified on Gru. Change-Id: I13852a1a05f567194c50e3c4b868b4cc27c06233 Reviewed-on: https://chromium-review.googlesource.com/424275 Commit-Ready: Hung-Te Lin <hungte@chromium.org> Tested-by: Hung-Te Lin <hungte@chromium.org> Reviewed-by: Youcheng Syu <youcheng@google.com>
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.