diff options
author | Maximilian Brune <maximilian.brune@9elements.com> | 2023-03-05 20:55:32 +0100 |
---|---|---|
committer | Lean Sheng Tan <sheng.tan@9elements.com> | 2023-03-28 13:27:50 +0000 |
commit | 347596ae6ee5ec50526f5dbf9300c183e1d48cd0 (patch) | |
tree | 8faa7f63f2202e5d9af92a370d9e222115e9b634 /configs/config.protectli_vp4630_vp4650 | |
parent | a3391e5f7a0d9d26c71092aaeab13d2fe5a133c6 (diff) |
util/ifdtool: Add option to create FMAP template
On systems that do not provide their own *.fmd (Flashmap) file, we
fall back to a default flashmap file. That file however does not contain
the blobs (ME, GBE ...), that are usually placed below the BIOS Flashmap.
It can therefore easily happen that the placement of the blobs collides
with the placement of the BIOS region (e.g. if CBFS_SIZE is big enough).
The fmaptool can't catch that, since it does not know of the blobs
placement.
This patch basically maps the regions described in the IFD (Intel
Firmware Descriptor) to the default Flashmap.
Test: Build and see that build/fmap.fmd contains all blobs now (on intel
systems that are supported by the ifdtool)
Signed-off-by: Maximilian Brune <maximilian.brune@9elements.com>
Change-Id: I82cb252fff456773af69943e188480a4998736fd
Reviewed-on: https://review.coreboot.org/c/coreboot/+/73487
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Lean Sheng Tan <sheng.tan@9elements.com>
Diffstat (limited to 'configs/config.protectli_vp4630_vp4650')
0 files changed, 0 insertions, 0 deletions