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.
TEST=Built and ran on glados.
Signed-off-by: Aaron Durbin <firstname.lastname@example.org>
Tested-by: build bot (Jenkins)
Tested-by: Raptor Engineering Automated Test Stand <email@example.com>
Reviewed-by: Patrick Georgi <firstname.lastname@example.org>
Reviewed-by: Stefan Reinauer <email@example.com>
26 files changed