summaryrefslogtreecommitdiff
path: root/src/include/elog.h
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2012-07-16 12:47:45 -0700
committerRonald G. Minnich <rminnich@gmail.com>2012-07-26 20:34:12 +0200
commit8de884424cb65bdba80a5602e76a4e40b11b154f (patch)
tree877377990e0a2426c3cfca9af201b9c7b2665d5f /src/include/elog.h
parentc1c9435863dd4bb22d06de486527d58b8a9e0170 (diff)
downloadcoreboot-8de884424cb65bdba80a5602e76a4e40b11b154f.tar.xz
ELOG: Fix reporting of developer/recovery modes
Recent changes in EC/Vboot/U-boot have completely broken the logging of developer and recovery modes. Recovery mode may not be in VBNV, so if that is zero and yet we are in recovery mode then assume it is there because the button/key was pressed. Since there may not be any actual developer mode switch we look if option rom is loaded and the system is not in recovery mode and consider that as developer mode. Change-Id: I70104877b24de477217e1ff5b3a019aef22343ec Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: http://review.coreboot.org/1346 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
Diffstat (limited to 'src/include/elog.h')
-rw-r--r--src/include/elog.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/include/elog.h b/src/include/elog.h
index 5a84c75d4b..488549eb1e 100644
--- a/src/include/elog.h
+++ b/src/include/elog.h
@@ -104,6 +104,7 @@ struct elog_event_data_wake {
/* Chrome OS related events */
#define ELOG_TYPE_CROS_DEVELOPER_MODE 0xa0
#define ELOG_TYPE_CROS_RECOVERY_MODE 0xa1
+#define ELOG_CROS_RECOVERY_MODE_BUTTON 0x02
/* Management Engine Events */
#define ELOG_TYPE_MANAGEMENT_ENGINE 0xa2