cbfs/vboot: remove firmware component support
The Chrome OS verified boot path supported multiple CBFS instances in the boot media as well as stand-alone assets sitting in each vboot RW slot. Remove the support for the stand-alone assets and always use CBFS accesses as the way to retrieve data. This is implemented by adding a cbfs_locator object which is queried for locating the current CBFS. Additionally, it is also signalled prior to when a program is about to be loaded by coreboot for the subsequent stage/payload. This provides the same opportunity as previous for vboot to hook in and perform its logic. BUG=chromium:445938 BRANCH=None TEST=Built and ran on glados. CQ-DEPEND=CL:307121,CL:31691,CL:31690 Change-Id: I6a3a15feb6edd355d6ec252c36b6f7885b383099 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/12689 Tested-by: build bot (Jenkins) Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com> Reviewed-by: Patrick Georgi <pgeorgi@google.com> Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
This commit is contained in:
@@ -99,14 +99,20 @@ static inline size_t region_sz(const struct region *r)
|
||||
return r->size;
|
||||
}
|
||||
|
||||
static inline const struct region *region_device_region(
|
||||
const struct region_device *rdev)
|
||||
{
|
||||
return &rdev->region;
|
||||
}
|
||||
|
||||
static inline size_t region_device_sz(const struct region_device *rdev)
|
||||
{
|
||||
return region_sz(&rdev->region);
|
||||
return region_sz(region_device_region(rdev));
|
||||
}
|
||||
|
||||
static inline size_t region_device_offset(const struct region_device *rdev)
|
||||
{
|
||||
return region_offset(&rdev->region);
|
||||
return region_offset(region_device_region(rdev));
|
||||
}
|
||||
|
||||
/* Memory map entire region device. Same semantics as rdev_mmap() above. */
|
||||
|
Reference in New Issue
Block a user