diff options
| author | Julius Werner <jwerner@chromium.org> | 2022-02-07 16:35:42 -0800 |
|---|---|---|
| committer | Julius Werner <jwerner@chromium.org> | 2022-02-09 17:38:39 +0000 |
| commit | 5a835161a24e08e35962f3e5737d042056679655 (patch) | |
| tree | 4c03c6d434e1dd4f57985ae0624d9f72ba656971 /src/console | |
| parent | b25261fc7ffdb1a98ffa7a9f6d16f3b51ef64b67 (diff) | |
| download | coreboot-5a835161a24e08e35962f3e5737d042056679655.tar.gz coreboot-5a835161a24e08e35962f3e5737d042056679655.tar.bz2 coreboot-5a835161a24e08e35962f3e5737d042056679655.zip | |
console/post: Lower post code loglevel to BIOS_INFO
Post codes don't signify an emergency error, so they shouldn't be
classified as BIOS_EMERG. Now that loglevels are more visible, this
misclassification looks pretty glaring. This patch changes them to
BIOS_INFO which seems more appropriate for an informational code that is
expected to occur in the normal boot flow.
Signed-off-by: Julius Werner <jwerner@chromium.org>
Change-Id: I85c8768232ae0cbf65669a7ee6abd538a3b2d5e1
Reviewed-on: https://review.coreboot.org/c/coreboot/+/61692
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Raul Rangel <rrangel@chromium.org>
Diffstat (limited to 'src/console')
| -rw-r--r-- | src/console/post.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/console/post.c b/src/console/post.c index 21ab00084a9a..1d99a2e9dd36 100644 --- a/src/console/post.c +++ b/src/console/post.c @@ -19,7 +19,7 @@ void post_code(uint8_t value) arch_post_code(value); if (CONFIG(CONSOLE_POST)) - printk(BIOS_EMERG, "POST: 0x%02x\n", value); + printk(BIOS_INFO, "POST: 0x%02x\n", value); mainboard_post(value); } |