soc/intel/broadwell: Unselect VBOOT_STARTS_IN_ROMSTAGE
Starting vboot earlier in bootblock instead of romstage is usually preferred (smaller root of trust, among other things). Therefore unselect VBOOT_STARTS_IN_ROMSTAGE for broadwell. Also remove the unused BROADWELL_VBOOT_IN_BOOTBLOCK option. Change-Id: If8feea403ee4cd3a16ed8cb0faf9f4ccb34feaaf Signed-off-by: Yu-Ping Wu <yupingso@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/66779 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
This commit is contained in:
parent
35835de942
commit
478c71e25b
|
@ -19,24 +19,9 @@ config BROADWELL_LPDDR3
|
||||||
Selected by mainboards using LPDDR3 DRAM to supply mainboard-specific
|
Selected by mainboards using LPDDR3 DRAM to supply mainboard-specific
|
||||||
LPDDR3 DQ and DQS CPU-to-DRAM mapping info needed to perform raminit.
|
LPDDR3 DQ and DQS CPU-to-DRAM mapping info needed to perform raminit.
|
||||||
|
|
||||||
config BROADWELL_VBOOT_IN_BOOTBLOCK
|
|
||||||
depends on VBOOT
|
|
||||||
bool "Start verstage in bootblock"
|
|
||||||
default y
|
|
||||||
select VBOOT_STARTS_IN_BOOTBLOCK
|
|
||||||
help
|
|
||||||
Broadwell can either start verstage in a separate stage
|
|
||||||
right after the bootblock has run or it can start it
|
|
||||||
after romstage for compatibility reasons.
|
|
||||||
Broadwell however uses a mrc.bin to initialize memory which
|
|
||||||
needs to be located at a fixed offset. Therefore even with
|
|
||||||
a separate verstage starting after the bootblock that same
|
|
||||||
binary is used meaning a jump is made from RW to the RO region
|
|
||||||
and back to the RW region after the binary is done.
|
|
||||||
|
|
||||||
config VBOOT
|
config VBOOT
|
||||||
select VBOOT_MUST_REQUEST_DISPLAY
|
select VBOOT_MUST_REQUEST_DISPLAY
|
||||||
select VBOOT_STARTS_IN_ROMSTAGE if !BROADWELL_VBOOT_IN_BOOTBLOCK
|
select VBOOT_STARTS_IN_BOOTBLOCK
|
||||||
|
|
||||||
config ECAM_MMCONF_BASE_ADDRESS
|
config ECAM_MMCONF_BASE_ADDRESS
|
||||||
default 0xf0000000
|
default 0xf0000000
|
||||||
|
|
Loading…
Reference in New Issue