diff options
| author | Arthur Heymans <arthur@aheymans.xyz> | 2019-01-03 21:11:45 +0100 |
|---|---|---|
| committer | Martin Roth <martinroth@google.com> | 2019-04-21 23:32:37 +0000 |
| commit | 77d5e7481b56ac396e02e73259d1fb414b375470 (patch) | |
| tree | 5754db12616243655be98cd4fecfa23f86e5e15d /src/mainboard/intel/baskingridge/Makefile.inc | |
| parent | 8e646e74b3d5e1d4a5e8114f03046f3d7b6ad042 (diff) | |
| download | coreboot-77d5e7481b56ac396e02e73259d1fb414b375470.tar.xz | |
nb/intel/haswell: Add an option for where verstage starts
Previously Haswell used a romcc bootblock and starting verstage in
romstage was madatory but with C_ENVIRONMENT_BOOTBLOCK it is also
possible to have a separate verstage.
This selects using a separate verstage by default but still keeps the
option around to use verstage in romstage.
Also make sure mrc.bin is only added to the COREBOOT fmap region as it
requires to be run at a specific offset. This means that coreboot will
have to jump from a RW region to the RO region for that binary and
back to that RW region after that binary is done initializing the
memory.
Change-Id: I3b7b29f4a24c0fb830ff76fe31a35b6afcae4e67
Signed-off-by: Arthur Heymans <arthur@aheymans.xyz>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/26926
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Patrick Rudolph <patrick.rudolph@9elements.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/intel/baskingridge/Makefile.inc')
| -rw-r--r-- | src/mainboard/intel/baskingridge/Makefile.inc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/mainboard/intel/baskingridge/Makefile.inc b/src/mainboard/intel/baskingridge/Makefile.inc index 5ef8363e35..06e86c1d6c 100644 --- a/src/mainboard/intel/baskingridge/Makefile.inc +++ b/src/mainboard/intel/baskingridge/Makefile.inc @@ -15,5 +15,6 @@ romstage-y += chromeos.c ramstage-y += chromeos.c +verstage-$(CONFIG_VBOOT_SEPARATE_VERSTAGE) += chromeos.c smm-$(CONFIG_HAVE_SMI_HANDLER) += mainboard_smi.c |