mirror of https://gitlab.com/qemu-project/qemu
55c136599f
When riscv_load_firmware() loads an ELF, the ELF segment addresses are used, not the passed-in firmware_load_addr. The machine models assume the firmware entry point is what they provided for firmware_load_addr, and use that address to generate the boot ROM, so if the ELF is linked at any other address, the boot ROM will jump to empty memory. Pass back the ELF entry point to use when generating the boot ROM, so the boot ROM can jump to firmware loaded anywhere in RAM. For example, on the virt machine, this allows using an OpenSBI fw_dynamic.elf built with FW_TEXT_START values other than 0x80000000. Signed-off-by: Samuel Holland <samuel.holland@sifive.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Message-ID: <20240817002651.3209701-1-samuel.holland@sifive.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| boot.c | ||
| meson.build | ||
| microchip_pfsoc.c | ||
| numa.c | ||
| opentitan.c | ||
| riscv_hart.c | ||
| shakti_c.c | ||
| sifive_e.c | ||
| sifive_u.c | ||
| spike.c | ||
| virt-acpi-build.c | ||
| virt.c | ||