From 4051405da98e250a9dc695454cf12d4d75d1b6dc Mon Sep 17 00:00:00 2001 From: Vic Yang Date: Tue, 22 May 2012 14:27:40 +0800 Subject: [PATCH] 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 Reviewed-by: Olof Johansson Commit-Ready: Vic Yang Tested-by: Vic Yang --- build_image | 2 +- mod_image_for_recovery.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/build_image b/build_image index 3b67a9e059..32fcccc377 100755 --- a/build_image +++ b/build_image @@ -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 # a display driver bug. if [ "${ARCH}" = "x86" -o "${ARCH}" = "amd64" ] ; then - export USE="${USE} initramfs" + export USE="${USE} initramfs vfat" fi # CONFIG_BLK_DEV_RAM is disabled by default. # But tftp install needs it to mount rootfs in ram diff --git a/mod_image_for_recovery.sh b/mod_image_for_recovery.sh index fd6c74c866..10df9a95d7 100755 --- a/mod_image_for_recovery.sh +++ b/mod_image_for_recovery.sh @@ -399,7 +399,7 @@ fi # Build the recovery kernel. 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" if [ -z "$FLAGS_kernel_image" ]; then