diff options
| author | Nick Kossifidis <[email protected]> | 2022-03-22 13:28:39 +0000 |
|---|---|---|
| committer | Palmer Dabbelt <[email protected]> | 2022-04-29 14:59:18 +0000 |
| commit | c6fe81191bd74f7e6ae9ce96a4837df9485f3ab8 (patch) | |
| tree | 28026403d851010d0b9b48f63127898b4c758817 /tools/perf/scripts/python | |
| parent | RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL (diff) | |
| download | kernel-c6fe81191bd74f7e6ae9ce96a4837df9485f3ab8.tar.gz kernel-c6fe81191bd74f7e6ae9ce96a4837df9485f3ab8.zip | |
RISC-V: relocate DTB if it's outside memory region
In case the DTB provided by the bootloader/BootROM is before the kernel
image or outside /memory, we won't be able to access it through the
linear mapping, and get a segfault on setup_arch(). Currently OpenSBI
relocates DTB but that's not always the case (e.g. if FW_JUMP_FDT_ADDR
is not specified), and it's also not the most portable approach since
the default FW_JUMP_FDT_ADDR of the generic platform relocates the DTB
at a specific offset that may not be available. To avoid this situation
copy DTB so that it's visible through the linear mapping.
Signed-off-by: Nick Kossifidis <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Tested-by: Conor Dooley <[email protected]>
Fixes: f105aa940e78 ("riscv: add BUILTIN_DTB support for MMU-enabled targets")
Cc: [email protected]
Signed-off-by: Palmer Dabbelt <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions