Julius Werner 8245bd25a3 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>		2019-12-11 11:42:26 +00:00
..
include/mainboard
board_info.txt
bootblock_custom.S
cbmem.c	lib/cbmem_top: Add a common cbmem_top implementation	2019-11-01 11:44:51 +00:00
devicetree.cb
Kconfig	Kconfig: comply to Linux 5.3's Kconfig language rules	2019-11-23 20:09:56 +00:00
Kconfig.name
mainboard.c
Makefile.inc	arch/arm64: Pass cbmem_top to ramstage via calling argument	2019-11-03 11:19:24 +00:00
media.c
memlayout.ld	fmap: Make FMAP_CACHE mandatory if it is configured in	2019-12-11 11:42:26 +00:00
mmio.c