summaryrefslogtreecommitdiff
path: root/util/nvmutil
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2023-05-14 08:16:12 +0100
committerLeah Rowe <leah@libreboot.org>2023-05-14 08:16:12 +0100
commit70e337afd08e6034f70cefbf8949a48dfbf5ec4a (patch)
treec2ec86a23f02b3f344f3e1f3a56ed4838c9b1759 /util/nvmutil
parent174297885820a8500997cce87a79090059059604 (diff)
blobutil/inject: use x86 top-aligned mrc offset
the old code was specifing an absolute offset for insertion of mrc.bin - cbfstool interprets anything above 0x80000000 as top-aligned memory address in x86, and anything below as an obsolute offset in the flash, like with the old number where a top-aligned address is provided to cbfstool, the absolute position is calculated for the flash, and cbfstool inserts it in the correct rom location the benefit of this change is that the absolute offset is now calculated automatically, which means that the code will be correct even if the flash size changes. for example, if 16MB flash is used whereas 12MB is currently the default an support haswell hardware coreboot does not provide anything readably like Kconfig, for extracting this value. it's baked into the source code of coreboot, so you have to find it. the correct location is hardcoded for each platform, and always the same on each platform, regardless of mainboard
Diffstat (limited to 'util/nvmutil')
0 files changed, 0 insertions, 0 deletions