summaryrefslogtreecommitdiffstats
path: root/src/southbridge/intel/lynxpoint/sata.c
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2022-03-01 17:53:40 -0800
committerRaul Rangel <rrangel@chromium.org>2022-03-04 16:04:10 +0000
commit2c423441c054d7a8c93cc814b9db5f8f7185bd0f (patch)
treedaf4789dbb0d3e95328ee8ad22ddff6d8ed72ca3 /src/southbridge/intel/lynxpoint/sata.c
parent872c34a57f5a198c2fb2e1c5c82b0ebbccf27b97 (diff)
downloadcoreboot-2c423441c054d7a8c93cc814b9db5f8f7185bd0f.tar.gz
coreboot-2c423441c054d7a8c93cc814b9db5f8f7185bd0f.tar.bz2
coreboot-2c423441c054d7a8c93cc814b9db5f8f7185bd0f.zip
libpayload: cbmem_console: Drop loglevel markers from snapshot
coreboot recently introduced non-printable loglevel markers in the CBMEM console. Payloads were generally unaffected since they don't use log levels and it is still legal to append lines without a marker to the log. However, payloads using cbmem_console_snapshot() to display existing logs from coreboot have started seeing '?' characters in place of the markers. This patch fixes the issue by filtering out marker characters. BUG=b:221909874 Signed-off-by: Julius Werner <jwerner@chromium.org> Change-Id: I4a9e5d464508320cf43ea572d62896d38c2a128d Reviewed-on: https://review.coreboot.org/c/coreboot/+/62506 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Raul Rangel <rrangel@chromium.org>
Diffstat (limited to 'src/southbridge/intel/lynxpoint/sata.c')
0 files changed, 0 insertions, 0 deletions