summaryrefslogtreecommitdiff
path: root/src/lib
diff options
context:
space:
mode:
authorFelix Held <felix-coreboot@felixheld.de>2021-05-25 19:15:11 +0200
committerFelix Held <felix-coreboot@felixheld.de>2021-05-27 15:41:15 +0000
commit2a29d4535036315ce62b0a6eba46b5de1d0778bb (patch)
tree6bf4ff8ffadef3c7ea49c1ed39c3cd4989d15a80 /src/lib
parenta30641295a1907aeef73f3a38677ef8ec94b6f85 (diff)
lib/hexdump: remove hexdump32 and use hexdump instead
hexdump and hexdump32 do similar things, but hexdump32 is mostly a reimplementation that has additional support to configure the console log level, but has a very unexpected len parameter that isn't in bytes, but in DWORDs. With the move to hexdump() the console log level for the hexdump is changed to BIOS_DEBUG. Signed-off-by: Felix Held <felix-coreboot@felixheld.de> Change-Id: I6138d17f0ce8e4a14f22d132bf5c64d0c343b80d Reviewed-on: https://review.coreboot.org/c/coreboot/+/54925 Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/lib')
-rw-r--r--src/lib/hexdump.c18
1 files changed, 0 insertions, 18 deletions
diff --git a/src/lib/hexdump.c b/src/lib/hexdump.c
index 90446c1481..533411f6f6 100644
--- a/src/lib/hexdump.c
+++ b/src/lib/hexdump.c
@@ -48,21 +48,3 @@ void hexdump(const void *memory, size_t length)
}
}
}
-
-void hexdump32(char LEVEL, const void *d, size_t len)
-{
- size_t count = 0;
-
- while (len > 0) {
- if (count % 8 == 0) {
- printk(LEVEL, "\n");
- printk(LEVEL, "%p:", d);
- }
- printk(LEVEL, " 0x%08lx", *(unsigned long *)d);
- count++;
- len--;
- d += 4;
- }
-
- printk(LEVEL, "\n\n");
-}