grunt: Mark RW_LEGACY as CBFS
Depthcharge is changing how the RW_LEGACY CBFS is handled for alternate bootloaders, see https://crrev.com/c/1528550 and https://crrev.com/c/1530303. This means that RW_LEGACY must be marked as CBFS in the fmap in order to work. All boards except for kahlee(grunt) have CBFS marked. BUG=b:128703316 TEST=Build and ran on grunt along with chromium patches on grunt and was able to list alternate bootloader with ctrl+l BRANCH=none Change-Id: I843d565a9503d27e666a34e59aba263ec490c81f Signed-off-by: Mathew King <mathewk@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/32019 Reviewed-by: Martin Roth <martinroth@google.com> Reviewed-by: Patrick Georgi <pgeorgi@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
parent
7169450310
commit
b08906b240
|
@ -24,7 +24,7 @@ FLASH@0xFF000000 0x1000000 {
|
|||
RW_NVRAM(PRESERVE)@0x467000 0x5000
|
||||
RW_UNUSED@0x46C000 0x14000
|
||||
SMMSTORE(PRESERVE)@0x480000 0x20000
|
||||
RW_LEGACY@0x4a0000 0x760000
|
||||
RW_LEGACY(CBFS)@0x4a0000 0x760000
|
||||
|
||||
WP_RO@0xC00000 0x400000 {
|
||||
RO_VPD(PRESERVE)@0x0 0x4000
|
||||
|
|
Loading…
Reference in New Issue