commit 4051405da98e250a9dc695454cf12d4d75d1b6dc
author Vic Yang <victoryang@chromium.org> Tue May 22 14:27:40 2012 +0800
committer Gerrit <chrome-bot@google.com> Wed May 23 17:49:46 2012 -0700
tree 8eb0a0a593db0e0a3af8cd789b4e277637c78e7f
parent c0ee2dd34e5908d7b403c5a4f80153a3baea7043

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>

build_image

diff --git a/build_image b/build_image
index 3b67a9e..32fcccc 100755
--- a/build_image
+++ b/build_image
@@ -150,7 +150,7 @@
   # 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

mod_image_for_recovery.sh

diff --git a/mod_image_for_recovery.sh b/mod_image_for_recovery.sh
index fd6c74c..10df9a9 100755
--- a/mod_image_for_recovery.sh
+++ b/mod_image_for_recovery.sh
@@ -399,7 +399,7 @@
 
 # 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