diff options
| author | Hung-Te Lin <hungte@chromium.org> | 2018-05-22 17:17:21 +0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-05-23 01:25:46 -0700 |
| commit | ecda11561bbb761ebe750425cae193db4e9b3560 (patch) | |
| tree | 8a4f6f20007687a943509714dfbc0b850a239457 /host/lib/include/crossystem_arch.h | |
| parent | 2c3d2c17ee9b379c4e076eaa574ffb671b7e4cb5 (diff) | |
| download | vboot-ecda11561bbb761ebe750425cae193db4e9b3560.tar.gz | |
crossystem: Add BINF3_LEGACY for systems boot in legacy mode.
The BINF3 (VBT7) reflects the firmware type, and we need that to
describe which type of firmware was booted.
The 'legacy' did not have its own value definition, but without that we
can't make sure if the system is running a non-chrome firmware or simply
entered legacy boot path. CL:1054307 introduced a new value (0x4) for
legacy type and we should handle it in crossystem mainfw_type command.
BUG=b:79130310
TEST=emerge-eve coreboot depthcharge chromeos-bootimage;
Boot in legacy mode and see crossystem reporting 'legacy' for
mainfw_type.
Change-Id: I4a1165e547e70c634d45054f56d1357ae5af2a83
Reviewed-on: https://chromium-review.googlesource.com/1068556
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'host/lib/include/crossystem_arch.h')
| -rw-r--r-- | host/lib/include/crossystem_arch.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/host/lib/include/crossystem_arch.h b/host/lib/include/crossystem_arch.h index 030d9d69..f02e0f73 100644 --- a/host/lib/include/crossystem_arch.h +++ b/host/lib/include/crossystem_arch.h @@ -23,6 +23,7 @@ #define BINF3_NORMAL 1 #define BINF3_DEVELOPER 2 #define BINF3_NETBOOT 3 +#define BINF3_LEGACY 4 /* INTERNAL APIS FOR CROSSYSTEM AVAILABLE TO ARCH-SPECIFIC FUNCTIONS */ |