From 106a0823c92593fe35150c5255d9852b9bff9c5d Mon Sep 17 00:00:00 2001 From: Michael Bacarella Date: Mon, 3 Dec 2018 11:23:43 -0800 Subject: 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 Change-Id: If47a88f06076da12d8da7a873c3e5ef64fc1f877 Reviewed-on: https://review.coreboot.org/c/30024 Reviewed-by: Angel Pons Reviewed-by: Patrick Georgi Tested-by: build bot (Jenkins) --- Documentation/flash_tutorial/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'Documentation/flash_tutorial') diff --git a/Documentation/flash_tutorial/index.md b/Documentation/flash_tutorial/index.md index 1a291372a6..eb74ad07c1 100644 --- a/Documentation/flash_tutorial/index.md +++ b/Documentation/flash_tutorial/index.md @@ -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 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 -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 -ifdtool -f rom.layout coreboot.rom +ifdtool -f rom.layout backup.rom ``` and looks similar to: -- cgit v1.2.3