From 357bb2daf09090192c09ddde501a7e07337614e1 Mon Sep 17 00:00:00 2001 From: Stefan Reinauer Date: Thu, 9 Aug 2012 13:44:38 -0700 Subject: 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 Reviewed-on: http://review.coreboot.org/1701 Reviewed-by: Marc Jones Tested-by: build bot (Jenkins) --- src/vendorcode/google/chromeos/Kconfig | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'src/vendorcode/google/chromeos/Kconfig') 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 -- cgit v1.2.3