summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2013-02-27 16:38:38 +0800
committerHung-Te Lin <hungte@chromium.org>2013-02-27 10:26:26 +0100
commitfdfd89f21326f13a279b37abfa05313434d48ac9 (patch)
tree134425c33001e98019e4bd65d5dd95582fdbd12e
parent62f100b02888c2de21d61caf5d850f1184e8be1a (diff)
downloadcoreboot-staging-fdfd89f21326f13a279b37abfa05313434d48ac9.zip
coreboot-staging-fdfd89f21326f13a279b37abfa05313434d48ac9.tar.gz
selfboot: Report correct entry point address in debug message.
Entry point in payload segment header is a 64 bit integer (ntohll). The debug message is currently reading that as a 32 bit integer (which will produce 00000000 for most platforms). Change-Id: I931072bbb82c099ce7fae04f15c8a35afa02e510 Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: http://review.coreboot.org/2535 Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Tested-by: build bot (Jenkins)
-rw-r--r--src/lib/selfboot.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/lib/selfboot.c b/src/lib/selfboot.c
index 56124da..d64ba4c 100644
--- a/src/lib/selfboot.c
+++ b/src/lib/selfboot.c
@@ -346,7 +346,8 @@ static int build_self_segment_list(
break;
case PAYLOAD_SEGMENT_ENTRY:
- printk(BIOS_DEBUG, " Entry Point 0x%p\n", (void *) ntohl((u32) segment->load_addr));
+ printk(BIOS_DEBUG, " Entry Point 0x%p\n",
+ (void *)(intptr_t)ntohll(segment->load_addr));
*entry = ntohll(segment->load_addr);
/* Per definition, a payload always has the entry point
* as last segment. Thus, we use the occurence of the
OpenPOWER on IntegriCloud