aboutsummaryrefslogtreecommitdiff
path: root/src/vendorcode/google/chromeos/Kconfig
diff options
context:
space:
mode:
authorStefan Reinauer <reinauer@chromium.org>2012-08-09 13:44:38 -0700
committerStefan Reinauer <stefan.reinauer@coreboot.org>2012-11-07 08:28:28 +0100
commit357bb2daf09090192c09ddde501a7e07337614e1 (patch)
treeaa5b66674f5b94e35a1b4a9d38b73aeb62b6a2ba /src/vendorcode/google/chromeos/Kconfig
parenta60ca36c4282c3998d4fc38d55e3dc668017b3ef (diff)
SandyBridge/IvyBridge: Use flash map to find MRC cache
Until now, the MRC cache position and size was hard coded in Kconfig. However, on ChromeOS devices, it should be determined by reading the FMAP. This patch provides a minimalistic FMAP parser (libflashmap was too complex and OS centered) to allow reading the in-ROM flash map and look for sections. This will also be needed on some partner devices where coreboot will have to find the VPD in order to set up the device's mac address correctly. The MRC cache implementation demonstrates how to use the FMAP parser. Change-Id: I34964b72587443a6ca4f27407d778af8728565f8 Signed-off-by: Stefan Reinauer <reinauer@google.com> Reviewed-on: http://review.coreboot.org/1701 Reviewed-by: Marc Jones <marcj303@gmail.com> Tested-by: build bot (Jenkins)
Diffstat (limited to 'src/vendorcode/google/chromeos/Kconfig')
-rw-r--r--src/vendorcode/google/chromeos/Kconfig7
1 files changed, 7 insertions, 0 deletions
diff --git a/src/vendorcode/google/chromeos/Kconfig b/src/vendorcode/google/chromeos/Kconfig
index 179bbb1f27..ace0c1805f 100644
--- a/src/vendorcode/google/chromeos/Kconfig
+++ b/src/vendorcode/google/chromeos/Kconfig
@@ -57,4 +57,11 @@ config CHROMEOS_RAMOOPS_RAM_SIZE
default 0x00100000
depends on CHROMEOS_RAMOOPS
+config FLASHMAP_OFFSET
+ hex
+ default 0x00670000 if NORTHBRIDGE_INTEL_SANDYBRIDGE
+ default 0x005f0000 if NORTHBRIDGE_INTEL_IVYBRIDGE
+ help
+ Offset of flash map in firmware image
+
endmenu