diff options
author | Alper Nebi Yasak <alpernebiyasak@gmail.com> | 2024-02-05 20:22:12 +0300 |
---|---|---|
committer | Nico Huber <nico.h@gmx.de> | 2024-08-16 16:17:29 +0000 |
commit | 8cc1d79ed0c3e523e080b9ae9bab35bb6d70d62e (patch) | |
tree | 598671bfab219ed3d3df2807fea486d2404e0689 /src/mainboard/google/poppy | |
parent | de1a74454ffaaca11c6735814ad1b97cc6e522cd (diff) |
mainboard/qemu-aarch64: Get top of memory from device-tree blob
Trying to probe RAM space to figure out top of memory causes an
exception on AArch64 virtual machines with recent versions of QEMU, but
we temporarily enable exception handlers for that and use it to help
detect if a RAM address is usable or not. However, QEMU docs recommend
reading device information from the device-tree blob it provides us at
the start of RAM.
A previous commit adds a library function to parse device-tree blob that
QEMU provides us. Use it to determine top of memory in AArch64 QEMU
virtual machines, but still fall back to the RAM probing approach as a
last-ditch effort.
Change-Id: I4cc888b57cf98e0797ce7f9ddfa2eb34d14cd9c1
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/80364
Reviewed-by: Maximilian Brune <maximilian.brune@9elements.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Julius Werner <jwerner@chromium.org>
Reviewed-by: Nico Huber <nico.h@gmx.de>
Diffstat (limited to 'src/mainboard/google/poppy')
0 files changed, 0 insertions, 0 deletions