From 9754cae1c1c4b267f228ee65df410e4115dc3d17 Mon Sep 17 00:00:00 2001 From: Marc Jones Date: Wed, 31 Oct 2012 17:19:44 -0600 Subject: Add FAFT keyboard remap GBB flag Add a new flag, 0x100, to indicate FAFT key stroke overrides. BUG=chrome-os-partner:14056 TEST=none BRANCH=stout Change-Id: I76b7f3f4c51abec5528047f690f20a09b257abc2 Signed-off-by: Marc Jones Reviewed-on: https://gerrit.chromium.org/gerrit/37074 Reviewed-by: Ronald G. Minnich Reviewed-by: Gediminas Ramanauskas Tested-by: Gediminas Ramanauskas Commit-Ready: Marc Jones --- scripts/image_signing/set_gbb_flags.sh | 1 + 1 file changed, 1 insertion(+) (limited to 'scripts') diff --git a/scripts/image_signing/set_gbb_flags.sh b/scripts/image_signing/set_gbb_flags.sh index de17c83d..ac52432d 100755 --- a/scripts/image_signing/set_gbb_flags.sh +++ b/scripts/image_signing/set_gbb_flags.sh @@ -30,6 +30,7 @@ GBBFLAGS_DESCRIPTION=" GBB_FLAG_DISABLE_FW_ROLLBACK_CHECK 0x00000020 GBB_FLAG_ENTER_TRIGGERS_TONORM 0x00000040 GBB_FLAG_FORCE_DEV_BOOT_LEGACY 0x00000080 + GBB_FLAG_FAFT_KEY_OVERIDE 0x00000100 To get a developer-friendly device, try 0x11 (short_delay + boot_usb). For factory-related tests (always DEV), try 0x39. -- cgit v1.2.1