On Wed, Oct 14, 2026 at 10:47:20PM +0800, Hung-Chun Tseng wrote: > When U-Boot runs from pflash on the QEMU RISC-V virt machine, QEMU > passes -kernel, -initrd and -append through fw_cfg and leaves booting > them to the firmware. U-Boot ignores them today: QFW is only enabled > with ACPI, and distro boot has no qfw target. > > This series brings the RISC-V QEMU targets in line with the Arm ones: > > 1. Enable CMD_QFW (and so QFW_MMIO) by default, and keep SPL_BLOBLIST > off in the SPL defconfigs, which would otherwise fail to link. > 2. Stop disabling initrd relocation, which checkpatch would reject in > the .env file of the next patch. > 3. Switch from distro boot to standard boot, with the environment in > qemu-riscv.env and qfw first in boot_targets. > 4. Document booting through fw_cfg. > > Tested with QEMU v11.1.2 and the Debian trixie riscv64 netboot kernel > and initrd (Linux 6.12): > > - qemu-riscv64_smode built for pflash, run with -kernel, -initrd and > -append and no input: U-Boot boots the kernel through qfw, the > kernel gets the command line and unpacks the initrd. > - qemu-riscv64_smode with a GPT disk holding an extlinux.conf on > virtio-blk: standard boot boots it with the extlinux method, as > distro boot did before the series. > - qemu-riscv64, qemu-riscv64_smode_acpi and qemu-riscv64_spl boot to > the prompt with the new boot_targets and bootcmd. > - qemu-riscv64_smode and qemu-riscv64_spl build at every patch.
For the whole series, Reviewed-by: Leo Yu-Chi Liang <[email protected]>
