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)
This commit is contained in:
parent
62f100b028
commit
fdfd89f213
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue