vboot: remove OPROM-related code
As of CL:1605641, vboot2 code should be used for setting and checking display init state. Remove all vboot1 OPROM-related code, and use the vboot2 display init code which has already been added in previous commits. coreboot should not be reading vboot NVRAM flags directly. Remove the function vboot_wants_oprom(), and instead rely on display_init_required(), which uses the VBOOT_WD_FLAG_DISPLAY_INIT value stored in vboot_working_data.flags, initialized during verstage. Note that this means in the case of CONFIG_VBOOT=y, the return value of display_init_required() can only be trusted after verstage has been executed. This should not be a problem assuming that all display initialization occurs in ramstage. BUG=b:124141368, b:124192753, chromium:948529 TEST=Build locally TEST=make clean && make test-abuild BRANCH=none Change-Id: Ic8f9dc5a3c7f1546a8fed82bde02be4d04568f8d Signed-off-by: Joel Kitching <kitching@google.com> Cq-Depend: chromium:1605641, chromium:1605525 Reviewed-on: https://review.coreboot.org/c/coreboot/+/32723 Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Julius Werner <jwerner@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
committed by
Patrick Georgi
parent
18b51b7315
commit
807803afa2
@@ -140,13 +140,6 @@ int get_recovery_mode_from_vbnv(void)
|
||||
return vbnv_data(RECOVERY_OFFSET);
|
||||
}
|
||||
|
||||
/* Read the BOOT_DISPLAY_REQUEST flag from VBNV. */
|
||||
int vboot_wants_oprom(void)
|
||||
{
|
||||
vbnv_setup();
|
||||
return (vbnv_data(BOOT_OFFSET) & BOOT_DISPLAY_REQUEST) ? 1 : 0;
|
||||
}
|
||||
|
||||
/* Read the USB Device Controller(UDC) enable flag from VBNV. */
|
||||
int vbnv_udc_enable_flag(void)
|
||||
{
|
||||
|
Reference in New Issue
Block a user