commit | a5a7579ec5a163cf3523a1cdae2e29e3ee2b39a7 | [log] [tgz] |
---|---|---|
author | You-Cheng Syu <youcheng@chromium.org> | Thu Jan 04 10:07:49 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Jan 04 15:35:41 2018 |
tree | 3254177346316f3df80c4524fcf1bb2afe527f4b | |
parent | a8612aad1764d88f3749ca5b916750a3e1c07c79 [diff] |
factory_shim: disable jobs arc-oemcrypto, swap, and syslog. arc-oemcrypto and swap would fail on some platform and block DUTs from entering into factory shim menu. Besides, after CL:664001, the way syslog starts rsyslogd changed. This affects factory shim, which doesn't contain rsyslogd, and make users have to wait for 60secs when booting into factory shim menu. Since these jobs are causing problems and they're not needed by factory shim, we could disable them. Also revise some comments for CL:497369. BUG=b:70966465 TEST=manually on Samus. Change-Id: Ie3bdebd8f9a6cff0b81a7739d4b95fd55d193e9a Reviewed-on: https://chromium-review.googlesource.com/850013 Commit-Ready: Youcheng Syu <youcheng@chromium.org> Tested-by: Youcheng Syu <youcheng@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.