Add 'vfat' flag when building kernel with initramfs

We are about to separate VFAT support from 'initramfs' flag. Let's add
'vfat' flag first so that when this happens nothing gets broken.

BUG=chrome-os-partner:9805
TEST=Build success. Factory install shim still works.

Change-Id: Ia432e3b1a6186f4f7c817a1283c86066ced5fef1
Reviewed-on: https://gerrit.chromium.org/gerrit/23193
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
This commit is contained in:
Vic Yang 2012-05-22 14:27:40 +08:00 committed by Gerrit
parent c0ee2dd34e
commit 4051405da9
2 changed files with 2 additions and 2 deletions

View File

@ -150,7 +150,7 @@ if should_build_image ${CHROMEOS_FACTORY_INSTALL_SHIM_NAME}; then
# network, so we don't require initramfs, but we do require fbconsole to fix # network, so we don't require initramfs, but we do require fbconsole to fix
# a display driver bug. # a display driver bug.
if [ "${ARCH}" = "x86" -o "${ARCH}" = "amd64" ] ; then if [ "${ARCH}" = "x86" -o "${ARCH}" = "amd64" ] ; then
export USE="${USE} initramfs" export USE="${USE} initramfs vfat"
fi fi
# CONFIG_BLK_DEV_RAM is disabled by default. # CONFIG_BLK_DEV_RAM is disabled by default.
# But tftp install needs it to mount rootfs in ram # But tftp install needs it to mount rootfs in ram

View File

@ -399,7 +399,7 @@ fi
# Build the recovery kernel. # Build the recovery kernel.
FACTORY_ROOT="${BOARD_ROOT}/factory-root" FACTORY_ROOT="${BOARD_ROOT}/factory-root"
USE="fbconsole initramfs" emerge_custom_kernel "$FACTORY_ROOT" || USE="fbconsole initramfs vfat" emerge_custom_kernel "$FACTORY_ROOT" ||
failboat "Cannot emerge custom kernel" failboat "Cannot emerge custom kernel"
if [ -z "$FLAGS_kernel_image" ]; then if [ -z "$FLAGS_kernel_image" ]; then