Documentation: Clarify minor detail on preparing a layout file
The user needs to pass the original firmware image to create a layout file, not the newly compiled coreboot image. Signed-off-by: Michael Bacarella <michael.bacarella@gmail.com> Change-Id: If47a88f06076da12d8da7a873c3e5ef64fc1f877 Reviewed-on: https://review.coreboot.org/c/30024 Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Patrick Georgi <pgeorgi@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
parent
be1907a513
commit
106a0823c9
|
@ -68,10 +68,11 @@ On platforms where the flash IC is shared with other components you might want
|
||||||
to write only a part of the flash IC. On Intel for example there are IFD, ME and
|
to write only a part of the flash IC. On Intel for example there are IFD, ME and
|
||||||
GBE which don't need to be updated to install coreboot.
|
GBE which don't need to be updated to install coreboot.
|
||||||
To make [flashrom] only write the *bios* region, leaving Intel ME and Intel IFD
|
To make [flashrom] only write the *bios* region, leaving Intel ME and Intel IFD
|
||||||
untouched, you can use a layout file, which can be created using ifdtool
|
untouched, you can use a layout file, which can be created with ifdtool and a backup
|
||||||
|
of the original firmware.
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
ifdtool -f rom.layout coreboot.rom
|
ifdtool -f rom.layout backup.rom
|
||||||
```
|
```
|
||||||
|
|
||||||
and looks similar to:
|
and looks similar to:
|
||||||
|
|
Loading…
Reference in New Issue