Upstream QEMU has decent support for RISC-V, so it’s possible for the Zephyr SDK to drop the RISC-V port and just build the "riscv32-softmmu” target on the latest stable QEMU.
Concurrently, the qemu_riscv32 board in Zephyr would need to be updated to use the same DTS as the HiFive1, since the QEMU target machine “sifive_e” emulates the exact same hardware and the old "sifive" target is gone.
Since RISC-V has its own QEMU recipe already, one option is just to retarget that against a newer upstream version, if upgrading QEMU for all architectures is undesirable right now. Any thoughts?
Upstream QEMU has decent support for RISC-V, so it’s possible for the Zephyr SDK to drop the RISC-V port and just build the "riscv32-softmmu” target on the latest stable QEMU.
Concurrently, the qemu_riscv32 board in Zephyr would need to be updated to use the same DTS as the HiFive1, since the QEMU target machine “sifive_e” emulates the exact same hardware and the old "sifive" target is gone.
Since RISC-V has its own QEMU recipe already, one option is just to retarget that against a newer upstream version, if upgrading QEMU for all architectures is undesirable right now. Any thoughts?