diff options
| author | Joel Kitching <kitching@google.com> | 2019-05-10 12:17:18 +0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-05-16 09:04:19 -0700 |
| commit | 43f6cab881dc0ed52fe08e6c2c64239fde11996b (patch) | |
| tree | b35951f4926755ca37ad5a55ffcdcc2b69fda519 /utility | |
| parent | 8c857f466aecf70d788fc3937af0e881545ea989 (diff) | |
| download | vboot-43f6cab881dc0ed52fe08e6c2c64239fde11996b.tar.gz | |
vboot: update display init to use vboot2 code
As per go/vboot2-oprom-cleanup, use vboot2 SD flag
DISPLAY_AVAILABLE, instead of the old vboot1 flags
OPROM_MATTERS and OPROM_LOADED.
Remove instances of "OPROM" and update with correct
nomenclature.
Update code and tests for EC software sync and diagnostic
menu to use vboot2 display init model.
OPROM_MATTERS and OPROM_LOADED are now deprecated, and
will be removed when no references remain in depthcharge
and coreboot.
Deprecate VBERROR_DISPLAY_INIT_MISMATCH (previously
OPROM_MISMATCH) and return VBERROR_REBOOT_REQUIRED
directly when needed.
BUG=b:124141368, b:124192753, chromium:948529
TEST=Build image for eve, force EC update,
check that the "critical update" screen shows
TEST=make clean && make runtests
BRANCH=none
Change-Id: I889872f886230f8559d5cce09d0de194da3fcc38
Signed-off-by: Joel Kitching <kitching@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1605641
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Joel Kitching <kitching@chromium.org>
Reviewed-by: Julius Werner <jwerner@chromium.org>
Diffstat (limited to 'utility')
| -rw-r--r-- | utility/crossystem.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/utility/crossystem.c b/utility/crossystem.c index 3093f2a8..00846a67 100644 --- a/utility/crossystem.c +++ b/utility/crossystem.c @@ -78,7 +78,7 @@ const Param sys_param_list[] = { {"mainfw_act", IS_STRING, "Active main firmware"}, {"mainfw_type", IS_STRING, "Active main firmware type"}, {"nvram_cleared", CAN_WRITE, "Have NV settings been lost? Write 0 to clear"}, - {"oprom_needed", CAN_WRITE, "Should we load the VGA Option ROM at boot?"}, + {"display_request", CAN_WRITE, "Should we initialize the display at boot?"}, {"phase_enforcement", 0, "Board should have full security settings applied"}, {"recovery_reason", 0, "Recovery mode reason for current boot"}, |