summaryrefslogtreecommitdiff
path: root/payloads/nvramcui
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2019-10-17 12:42:28 +0800
committerPatrick Georgi <pgeorgi@google.com>2019-10-18 12:23:54 +0000
commit064d6cb8a53b022244082cb2c2ebce2f5fb02486 (patch)
treec3e59e24bb6fa0aae70ae0125a1e2688a1e2b916 /payloads/nvramcui
parenta2ea5e9f47d97237cd98bea6f29fb9dd17167721 (diff)
downloadcoreboot-064d6cb8a53b022244082cb2c2ebce2f5fb02486.tar.xz
mb/google: Shrink GBB section size
Chrome OS firmware images have moved bitmap resources from GBB into CBFS for a long time, so the GBB should only hold firmware keys and HWID, that is usually less than 10k. ARM boards usually limit GBB to 0x2f00 (see gru, cheza and kukui) but many recent x86 simply copy from old settings and may run out of space when we want to add more resources, for example EC RO software sync. Note, changing the GBB section (inside RO) implies RO update, so this change *must not* be cherry-picked back to old firmware branches if some devices were already shipped. BRANCH=none BUG=None TEST=make # board=darllion,hatch,kahlee,octopus,sarien Change-Id: I615cd7b53b556019f2d54d0df7ac2723d36ee6cf Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/36088 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Georgi <pgeorgi@google.com> Reviewed-by: Mathew King <mathewk@chromium.org> Reviewed-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'payloads/nvramcui')
0 files changed, 0 insertions, 0 deletions