Julius Werner uploaded patch set #2 to this change.

View Change

bootmode: display_init_required() to check VBOOT and OPROM_MATTERS

Skipping display init on normal-mode boot is a vboot feature, not
specific to Chrome OS. Fix the code in display_init_required() to check
CONFIG_VBOOT rather than CONFIG_CHROMEOS now that the two aren't always
the same anymore.

Also add a check to guarantee at compile time that VBOOT_OPROM_MATTERS
is enabled on all platforms that make a check to this function (when
VBOOT is also enabled). The whole display skipping mechanism is based on
the oprom_needed NVRAM flag, and skipping display init without enabling
the option to tell vboot that it needs to pay attention to that flag
would make the whole thing not work right.

Change-Id: I5d6421509bdcdaa61b78015af3fa6241fe75bb7f
Signed-off-by: Julius Werner <jwerner@chromium.org>
---
M src/lib/bootmode.c
1 file changed, 6 insertions(+), 1 deletion(-)

git pull ssh://review.coreboot.org:29418/coreboot refs/changes/12/32112/2

To view, visit change 32112. To unsubscribe, or for help writing mail filters, visit settings.

Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I5d6421509bdcdaa61b78015af3fa6241fe75bb7f
Gerrit-Change-Number: 32112
Gerrit-PatchSet: 2
Gerrit-Owner: Julius Werner <jwerner@chromium.org>
Gerrit-Reviewer: Furquan Shaikh <furquan@google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply@coreboot.org>
Gerrit-CC: Paul Menzel <paulepanter@users.sourceforge.net>
Gerrit-MessageType: newpatchset