coreboot-kgpe-d16/src/mainboard/google/veyron_emile/chromeos.fmd

FLASH@0x0 0x400000 {
	WP_RO@0x0 0x200000 {
		RO_SECTION@0x0 0x1f0000 {
			BOOTBLOCK@0 128K
			COREBOOT(CBFS)@0x20000 0xe0000
			FMAP@0x100000 0x1000
			GBB@0x101000 0xeef00
			RO_FRID@0x1eff00 0x100
		}
		RO_VPD@0x1f0000 0x10000
	}
	RW_SECTION_A@0x200000 0x78000 {
		VBLOCK_A@0x0 0x2000
		FW_MAIN_A(CBFS)@0x2000 0x75f00
		RW_FWID_A@0x77f00 0x100
	}
	RW_SHARED@0x278000 0x2000 {
		SHARED_DATA@0x0 0x2000
	}
	RW_NVRAM@0x27a000 0x2000
	RW_ELOG@0x27c000 0x4000
	RW_SECTION_B@0x280000 0x78000 {
		VBLOCK_B@0x0 0x2000
		FW_MAIN_B(CBFS)@0x2000 0x75f00
		RW_FWID_B@0x77f00 0x100
	}
	RW_VPD@0x2f8000 0x8000
	RW_LEGACY(CBFS)@0x300000 0x100000
}
chromeos: import Chrome OS fmaps These are generated from depthcharge's board/*/fmap.dts using the dts-to-fmd.sh script. One special case is google/veyron's chromeos.fmd, which is used for a larger set of boards - no problem since the converted fmd was the same for all of them. Set aside 128K for the bootblock on non-x86 systems (where the COREBOOT region ends up at the beginning of flash). This becomes necessary because we're working without a real cbfs master header (exists for transition only), which carved out the space for the offset. Change-Id: Ieeb33702d3e58e07e958523533f83da97237ecf1 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: https://review.coreboot.org/12715 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com> 2015-12-12 00:23:15 +01:00			`FLASH@0x0 0x400000 {`
			`WP_RO@0x0 0x200000 {`
			`RO_SECTION@0x0 0x1f0000 {`
			`BOOTBLOCK@0 128K`
			`COREBOOT(CBFS)@0x20000 0xe0000`
			`FMAP@0x100000 0x1000`
			`GBB@0x101000 0xeef00`
			`RO_FRID@0x1eff00 0x100`
			`}`
			`RO_VPD@0x1f0000 0x10000`
			`}`
			`RW_SECTION_A@0x200000 0x78000 {`
			`VBLOCK_A@0x0 0x2000`
			`FW_MAIN_A(CBFS)@0x2000 0x75f00`
			`RW_FWID_A@0x77f00 0x100`
			`}`
			`RW_SHARED@0x278000 0x2000 {`
			`SHARED_DATA@0x0 0x2000`
			`}`
			`RW_NVRAM@0x27a000 0x2000`
			`RW_ELOG@0x27c000 0x4000`
			`RW_SECTION_B@0x280000 0x78000 {`
			`VBLOCK_B@0x0 0x2000`
			`FW_MAIN_B(CBFS)@0x2000 0x75f00`
			`RW_FWID_B@0x77f00 0x100`
			`}`
			`RW_VPD@0x2f8000 0x8000`
chromeos.fmd: Mark RW_LEGACY as CBFS Change the existing chromeos.fmd files and the dts-to-fmd script to mark RW_LEGACY as CBFS, so it's properly "formatted". BUG=chromium:595715 BRANCH=none TEST=none Change-Id: I76de26032ea8da0c7755a76a01e7bea9cfaebe23 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: 717a00c459906fa87f61314ea4541c31b50539f4 Original-Change-Id: I4b037b60d10be3da824c6baecabfd244eec2cdac Original-Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Reviewed-on: https://chromium-review.googlesource.com/336403 Original-Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Original-Tested-by: Patrick Georgi <pgeorgi@chromium.org> Original-Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: https://review.coreboot.org/14240 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com> 2016-03-31 15:59:41 +02:00			`RW_LEGACY(CBFS)@0x300000 0x100000`
chromeos: import Chrome OS fmaps These are generated from depthcharge's board/*/fmap.dts using the dts-to-fmd.sh script. One special case is google/veyron's chromeos.fmd, which is used for a larger set of boards - no problem since the converted fmd was the same for all of them. Set aside 128K for the bootblock on non-x86 systems (where the COREBOOT region ends up at the beginning of flash). This becomes necessary because we're working without a real cbfs master header (exists for transition only), which carved out the space for the offset. Change-Id: Ieeb33702d3e58e07e958523533f83da97237ecf1 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: https://review.coreboot.org/12715 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com> 2015-12-12 00:23:15 +01:00			`}`