summaryrefslogtreecommitdiff
path: root/firmware/stub/vboot_api_stub.c
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2019-03-01 14:23:30 -0800
committerchrome-bot <chrome-bot@chromium.org>2019-03-09 01:18:53 -0800
commit9e53b92e50165b777111f159daa2b4e3b3c8b355 (patch)
treebd354022acf50dafa0da42ca6e0f0590a0a2f3c9 /firmware/stub/vboot_api_stub.c
parente20d92ab46a9a60925ede8892c59eba10b34c4d1 (diff)
downloadvboot-9e53b92e50165b777111f159daa2b4e3b3c8b355.tar.gz
vboot_display: Add full_info parameter to VbExDisplayDebugInfo()factory-atlas-11907.Bfactory-atlas-11907.11.B
VbExDisplayDebugInfo() was invented for the TAB display that dumps a whole lot of possibly interesting debug data to the screen. Since some debug data is only available to the calling firmware, the convention has always been that the calling firmware is supposed to append any of its own debug data it thinks may be relevant to the output. Later, the function was reused to print small info messages that give the user a hint what went wrong when a Ctrl+U or Ctrl+L fails (unlocalized, of course, but better than nothing). The calling firmware is not aware of this new use case, so every time vboot prints a "WARNING: Ctrl+L not enabled" sort of message on the screen, depthcharge also dumps the firmware IDs and TPM state below it. This patch introduces a new parameter to the function to make the two differing use cases clear to the calling firmware. CQ-DEPEND=CL:1496903 BRANCH=None BUG=None TEST=with other patches Change-Id: I52a1e764189508130fea562ad6d53bcefb1fce64 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1497038
Diffstat (limited to 'firmware/stub/vboot_api_stub.c')
-rw-r--r--firmware/stub/vboot_api_stub.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/firmware/stub/vboot_api_stub.c b/firmware/stub/vboot_api_stub.c
index 599b80c7..3363aa4f 100644
--- a/firmware/stub/vboot_api_stub.c
+++ b/firmware/stub/vboot_api_stub.c
@@ -39,7 +39,7 @@ VbError_t VbExDisplayMenu(uint32_t screen_type, uint32_t locale,
return VBERROR_SUCCESS;
}
-VbError_t VbExDisplayDebugInfo(const char *info_str)
+VbError_t VbExDisplayDebugInfo(const char *info_str, int full_info)
{
return VBERROR_SUCCESS;
}