Eliminate use of pointers in coreboot table
Because pointers can be 32bit or 64bit big,
using them in the coreboot table requires the
OS and the firmware to operate in the same mode
which is not always the case. Hence, use 64bit
for all pointers stored in the coreboot table.
Guess we'll have to fix this up once we port to
the first 128bit machines.
BUG=chrome-os-partner:18638
TEST=USE=depthcharge emerge-link libpayload depthcharge chromeos-coreboot-link chromeos-bootimage
produces working image
BRANCH=none
Change-Id: I46fc1dad530e5230986f7aa5740595428ede4f93
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/48723
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
bde97c09ad
commit
cdac2d378d
5 changed files with 9 additions and 9 deletions
|
|
@ -218,7 +218,7 @@ struct lb_vdat {
|
|||
uint32_t tag;
|
||||
uint32_t size;
|
||||
|
||||
void *vdat_addr;
|
||||
uint64_t vdat_addr;
|
||||
uint32_t vdat_size;
|
||||
};
|
||||
|
||||
|
|
@ -246,7 +246,7 @@ struct lb_vboot_handoff {
|
|||
uint32_t tag;
|
||||
uint32_t size;
|
||||
|
||||
void *vboot_handoff_addr;
|
||||
uint64_t vboot_handoff_addr;
|
||||
uint32_t vboot_handoff_size;
|
||||
};
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue