cbfs: Remove locator concept

When vboot was first integrated into CBFS it was still part of Google
vendorcode. So to not directly tie custom vendorcode into the core CBFS
library, the concept of cbfs_locator was introduced to decouple core
code from an arbitrary amount of platform-specific implementations that
want to decide where the CBFS can be found.

Nowadays vboot is a core coreboot feature itself, and the locator
concept isn't used by anything else anymore. This patch simplifies the
code by removing it and just calling vboot from the CBFS library
directly. That should make it easier to more closely integrate vboot
into CBFS in the future.

Change-Id: I7b9112adc7b53aa218c58b8cb5c85982dcc1dbc0
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/38419
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
This commit is contained in:
Julius Werner
2019-12-05 22:29:07 -08:00
committed by Patrick Georgi
parent 029d67278b
commit 815611ef56
4 changed files with 7 additions and 91 deletions

View File

@@ -70,7 +70,7 @@ void vboot_run_logic(void)
}
}
static int vboot_locate(struct region_device *rdev)
int vboot_locate_cbfs(struct region_device *rdev)
{
struct vb2_context *ctx;
@@ -85,8 +85,3 @@ static int vboot_locate(struct region_device *rdev)
return vboot_locate_firmware(ctx, rdev);
}
const struct cbfs_locator vboot_locator = {
.name = "VBOOT",
.locate = vboot_locate,
};