mod_image_for_recovery.sh: drop fbconsole/vtconsole settings
We rely on frecon now for the tty, so drop these old knobs.
BUG=chromium:774377
TEST=booting recovery image on elm worked
Change-Id: If70fadb4cdd39e512d66639281bf3cb6af650fe2
Reviewed-on: https://chromium-review.googlesource.com/1483763
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
diff --git a/mod_image_for_recovery.sh b/mod_image_for_recovery.sh
index c16e874..21445e6 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"
-RECOVERY_KERNEL_FLAGS="fbconsole vtconsole recovery_ramfs tpm i2cdev vfat kernel_compress_xz -kernel_afdo"
+RECOVERY_KERNEL_FLAGS="recovery_ramfs tpm i2cdev vfat kernel_compress_xz -kernel_afdo"
USE="${RECOVERY_KERNEL_FLAGS}" emerge_custom_kernel "$FACTORY_ROOT" ||
die "Cannot emerge custom kernel"
