Re: [PATCH V5 3/3] hw/riscv: virt: Enable booting S-mode firmware from pflash

2022-10-11 Thread Bernhard Beschow
Am 4. Oktober 2022 09:23:51 UTC schrieb Sunil V L : >To boot S-mode firmware payload like EDK2 from persistent >flash storage, qemu needs to pass the flash address as the >next_addr in fw_dynamic_info to the opensbi. > >When both -kernel and -pflash options are provided in command line, >the kernel

Re: [PATCH V5 3/3] hw/riscv: virt: Enable booting S-mode firmware from pflash

2022-10-09 Thread Alistair Francis
On Tue, Oct 4, 2022 at 7:28 PM Sunil V L wrote: > > To boot S-mode firmware payload like EDK2 from persistent > flash storage, qemu needs to pass the flash address as the > next_addr in fw_dynamic_info to the opensbi. > > When both -kernel and -pflash options are provided in command line, > the ke

[PATCH V5 3/3] hw/riscv: virt: Enable booting S-mode firmware from pflash

2022-10-04 Thread Sunil V L
To boot S-mode firmware payload like EDK2 from persistent flash storage, qemu needs to pass the flash address as the next_addr in fw_dynamic_info to the opensbi. When both -kernel and -pflash options are provided in command line, the kernel (and initrd if -initrd) will be copied to fw_cfg table. T