cbfstool: have update-fit always work from CBFS
On x86, the bootblock can (and will) become part of the regular file system, so there's no distinct fixed-size region for the bootblock there. Change-Id: Ie139215b73e01027bc0586701361e9a0afa9150e Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: http://review.coreboot.org/11691 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
9cc8e92b6c
commit
6dd99fcafe
|
@ -838,16 +838,9 @@ static int cbfs_update_fit(void)
|
||||||
return 1;
|
return 1;
|
||||||
}
|
}
|
||||||
|
|
||||||
// Decide which region to read/write the FIT table from/to.
|
|
||||||
struct buffer bootblock;
|
struct buffer bootblock;
|
||||||
if (partitioned_file_is_partitioned(param.image_file)) {
|
// The bootblock is part of the CBFS on x86
|
||||||
if (!partitioned_file_read_region(&bootblock, param.image_file,
|
buffer_clone(&bootblock, param.image_region);
|
||||||
SECTION_WITH_FIT_TABLE))
|
|
||||||
return 1;
|
|
||||||
} else {
|
|
||||||
// In legacy images, the bootblock is part of the CBFS.
|
|
||||||
buffer_clone(&bootblock, param.image_region);
|
|
||||||
}
|
|
||||||
|
|
||||||
struct cbfs_image image;
|
struct cbfs_image image;
|
||||||
if (cbfs_image_from_buffer(&image, param.image_region,
|
if (cbfs_image_from_buffer(&image, param.image_region,
|
||||||
|
|
Loading…
Reference in New Issue