summaryrefslogtreecommitdiff
path: root/src/Kconfig
diff options
context:
space:
mode:
authorKyösti Mälkki <kyosti.malkki@gmail.com>2014-01-06 11:06:26 +0200
committerKyösti Mälkki <kyosti.malkki@gmail.com>2014-01-15 15:26:48 +0100
commit107f72e674a3fbe2cadb24d98bba53f432bc2e0c (patch)
tree57cd61737cba76ca8413aeea360f780ad1be22c8 /src/Kconfig
parent5e73be2a7a6d69cf860afba82b38803c2a792006 (diff)
Re-declare CACHE_ROM_SIZE as aligned ROM_SIZE for MTRR
This change allows Kconfig options ROM_SIZE and CBFS_SIZE to be set with values that are not power of 2. The region programmed as WB cacheable will include all of ROM_SIZE. Side-effects to consider: Memory region below flash may be tagged WRPROT cacheable. As an example, with ROM_SIZE of 12 MB, CACHE_ROM_SIZE would be 16 MB. Since this can overlap CAR, we add an explicit test and fail on compile should this happen. To work around this problem, one needs to use CACHE_ROM_SIZE_OVERRIDE in the mainboard Kconfig and define a smaller region for WB cache. With this change flash regions outside CBFS are also tagged WRPROT cacheable. This covers IFD and ME and sections ChromeOS may use. Change-Id: I5e577900ff7e91606bef6d80033caaed721ce4bf Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: http://review.coreboot.org/4625 Tested-by: build bot (Jenkins) Reviewed-by: Vladimir Serbinenko <phcoder@gmail.com>
Diffstat (limited to 'src/Kconfig')
-rw-r--r--src/Kconfig4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/Kconfig b/src/Kconfig
index 88df9ae8a8..bed6c7f8ee 100644
--- a/src/Kconfig
+++ b/src/Kconfig
@@ -385,9 +385,9 @@ config CBFS_SIZE
hex
default ROM_SIZE
-config CACHE_ROM_SIZE
+config CACHE_ROM_SIZE_OVERRIDE
hex
- default CBFS_SIZE
+ default 0
# TODO: Can probably be removed once all chipsets have kconfig options for it.
config VIDEO_MB