547a059b34
Since there's currently a limitation in coreboot's code that prevents more than 4KB to be used by the eventlog anyway, this patch shrinks the available RW_ELOG area in the FMAP for Gru down to 4KB. This may prove prudent later if we ever resolve that limitation, so that tools can rely on the area in the FMAP being the same as the area actually used by the read-only firmware code on these boards. BRANCH=gru BUG=chrome-os-partner:55593 TEST=Booted Kevin, confirmed that eventlog got written normally. Ran a reboot loop to exhaust eventlog space, confirmed that the shrink code kicks in as expected before reaching 4KB. Change-Id: I3c55d836c72486665a19783fe98ce9e0df174b6d Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: 05efb82ca00703fd92d925ebf717738e37295c18 Original-Change-Id: Ia2617681f9394e953f5beb4abf419fe8d97e6d3e Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/384585 Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-by: Simon Glass <sjg@google.com> Reviewed-on: https://review.coreboot.org/16715 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com>
30 lines
666 B
Text
30 lines
666 B
Text
FLASH@0x0 0x800000 {
|
|
WP_RO@0x0 0x400000 {
|
|
RO_SECTION@0x0 0x3e0000 {
|
|
BOOTBLOCK@0 128K
|
|
COREBOOT(CBFS)@0x20000 0x2e0000
|
|
FMAP@0x300000 0x1000
|
|
GBB@0x301000 0xdef00
|
|
RO_FRID@0x3dff00 0x100
|
|
}
|
|
RO_VPD@0x3e0000 0x20000
|
|
}
|
|
RW_SECTION_A@0x400000 0xe8000 {
|
|
VBLOCK_A@0x0 0x2000
|
|
FW_MAIN_A(CBFS)@0x2000 0xe5f00
|
|
RW_FWID_A@0xe7f00 0x100
|
|
}
|
|
RW_VPD@0x4e8000 0x8000
|
|
RW_SECTION_B@0x4f0000 0xe8000 {
|
|
VBLOCK_B@0x0 0x2000
|
|
FW_MAIN_B(CBFS)@0x2000 0xe5f00
|
|
RW_FWID_B@0xe7f00 0x100
|
|
}
|
|
RW_ELOG@0x5d8000 0x1000
|
|
RW_UNUSED@0x5d9000 0x7000
|
|
RW_SHARED@0x5e0000 0x10000 {
|
|
SHARED_DATA@0x0 0x10000
|
|
}
|
|
RW_NVRAM@0x5f0000 0x10000
|
|
RW_LEGACY(CBFS)@0x600000 0x200000
|
|
}
|