summaryrefslogtreecommitdiff
path: root/tests/vb2_ui_tests.c
diff options
context:
space:
mode:
authorPatrick Georgi <pgeorgi@google.com>2020-06-28 21:07:16 +0000
committerCommit Bot <commit-bot@chromium.org>2020-07-02 11:31:05 +0000
commit68de90c7e2f4a27d3a76489199176d2ab8f56de1 (patch)
tree81d04d60a551bd36c70a107b06f106b6144e2023 /tests/vb2_ui_tests.c
parent4b3e5288ec913f2f4f9e9ce9fda5dae1aba92186 (diff)
downloadvboot-68de90c7e2f4a27d3a76489199176d2ab8f56de1.tar.gz
Allow building for non-CrOS environments
There's some code that is architecture specific, but looking at it, it's code for Chrome OS devices that just happens to be split along ISA lines. When building on systems that we don't ship crossystems integration for, these parts are replaced by stubs that always return error conditions, which allows building on unsupported ISA (such as POWER). The issue was reported at https://ticket.coreboot.org/issues/145 where a coreboot user wanted to build a vboot-enabled coreboot configuration (which builds futility for the signing part) on a POWER host system, which failed because we lack an implementation of the crossystem interfaces for POWER. BUG=none BRANCH=none TEST=Built upstream coreboot with a vboot-enabled target inside qemu-user-ppc64. Doing so works with these patches applied while it failed without them. Change-Id: I4aaeb56d4521c426a520bc9a1bb49497bec86c35 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/2270096 Commit-Queue: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Joel Kitching <kitching@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org>
Diffstat (limited to 'tests/vb2_ui_tests.c')
0 files changed, 0 insertions, 0 deletions