fmap: Make FMAP_CACHE mandatory if it is configured in
Now that we have a CONFIG_NO_FMAP_CACHE to completely configure out the pre-RAM FMAP cache code, there's no point in allowing the region to be optional anymore. This patch makes the section required by the linker. If a board doesn't want to provide it, it has to select NO_FMAP_CACHE. Adding FMAP_CACHE regions to a couple more targets that I think can use them but I don't know anything about... please yell if one of these is a bad idea and I should mark them NO_FMAP_CACHE instead. Change-Id: Ic7d47772ab3abfa7e3a66815c3739d0af071abc2 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37497 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Furquan Shaikh <furquan@google.com>
This commit is contained in:
committed by
Patrick Georgi
parent
ad27283a3c
commit
8245bd25a3
@@ -19,7 +19,8 @@ SECTIONS
|
||||
{
|
||||
DRAM_START(0x40000000)
|
||||
BOOTBLOCK(0x402f0400, 20K)
|
||||
ROMSTAGE(0x402f5400, 90K)
|
||||
ROMSTAGE(0x402f5400, 88K)
|
||||
FMAP_CACHE(0x4030b400, 2K)
|
||||
STACK(0x4030be00, 4K)
|
||||
RAMSTAGE(0x80200000, 192K)
|
||||
|
||||
|
Reference in New Issue
Block a user