diff options
| author | Julius Werner <jwerner@chromium.org> | 2019-06-24 19:41:25 -0700 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2019-06-28 06:50:36 +0000 |
| commit | 11c512664e0b9c30307bf96ae01edead27939dfd (patch) | |
| tree | e3bec4684b4c70fcfd3646cc7f87538131f4bd00 | |
| parent | 1851825b05d266509c4157d1413c0d853a9add28 (diff) | |
| download | vboot-11c512664e0b9c30307bf96ae01edead27939dfd.tar.gz | |
firmware: Print GBB flags at the start of kernel verification
I've had dozens of instances over the years where I had been wondering
what GBB flags a given firmware log was running with. Let's just print
them.
BRANCH=None
BUG=None
TEST=Booted Cheza.
Change-Id: I631dbcffd16f189731ed5881782722e1eec8eb83
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/1674967
Reviewed-by: Joel Kitching <kitching@chromium.org>
| -rw-r--r-- | firmware/lib/vboot_api_kernel.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/firmware/lib/vboot_api_kernel.c b/firmware/lib/vboot_api_kernel.c index 7e48685a..9135085e 100644 --- a/firmware/lib/vboot_api_kernel.c +++ b/firmware/lib/vboot_api_kernel.c @@ -394,6 +394,8 @@ VbError_t VbSelectAndLoadKernel( if (retval) goto VbSelectAndLoadKernel_exit; + VB2_DEBUG("GBB flags are %#x\n", vb2_get_gbb(ctx)->flags); + /* * Do EC software sync unless we're in recovery mode. This has UI but * it's just a single non-interactive WAIT screen. |