summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2013-07-26 15:07:57 -0500
committerChromeBot <chrome-bot@google.com>2013-07-26 15:02:01 -0700
commitd79f111427ab11919d9f91aa4f54c893f9e9986a (patch)
tree912ebb0bc83ef8d762ea1bfedf94028c967a7615
parentd41000ed64bb144704fcbf2db3db840de30d069d (diff)
downloadvboot-factory-pit-4471.B.tar.gz
VbInit(): printout gbb flags as wellfactory-pit-4471.B
It's extremely helpful to know what a device's gbb flags are when running vboot. It aids in debugging issues by providing more information and context. BUG=None BRANCH=None TEST=Built and booted. Checked log. Change-Id: I663de6f617f0e8c74e2b2f3b7a2be63f4a9c020a Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/63489 Reviewed-by: Randall Spangler <rspangler@chromium.org>
-rw-r--r--firmware/lib/vboot_api_init.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/firmware/lib/vboot_api_init.c b/firmware/lib/vboot_api_init.c
index 5174aa1f..c55e708c 100644
--- a/firmware/lib/vboot_api_init.c
+++ b/firmware/lib/vboot_api_init.c
@@ -36,7 +36,8 @@ VbError_t VbInit(VbCommonParams *cparams, VbInitParams *iparams)
uint32_t clear_tpm_owner_request = 0;
int is_dev = 0;
- VBDEBUG(("VbInit() input flags 0x%x\n", iparams->flags));
+ VBDEBUG(("VbInit() input flags 0x%x gbb flags 0x%x\n", iparams->flags,
+ gbb->flags));
/* Initialize output flags */
iparams->out_flags = 0;