On Wed, May 31, 2023 at 04:34:58AM -0700, Andrea Bolognani wrote:
> On Wed, May 31, 2023 at 10:46:17AM +0530, Anup Patel wrote:
> > On Fri, May 26, 2023 at 5:41 PM Sunil V L wrote:
> > > hw/riscv: virt: Assume M-mode FW in pflash0 only when "-bios none"
> > > riscv/virt: Support using pflash v
On Wed, May 31, 2023 at 10:46:17AM +0530, Anup Patel wrote:
> On Fri, May 26, 2023 at 5:41 PM Sunil V L wrote:
> > hw/riscv: virt: Assume M-mode FW in pflash0 only when "-bios none"
> > riscv/virt: Support using pflash via -blockdev option
> > docs/system: riscv: Add pflash usage details
>
>
On Fri, May 26, 2023 at 5:41 PM Sunil V L wrote:
>
> This series improves the pflash usage in RISC-V virt machine with solutions to
> below issues.
>
> 1) Currently the first pflash is reserved for ROM/M-mode firmware code. But
> S-mode
> payload firmware like EDK2 need both pflash devices to hav
On Fri, May 26, 2023 at 05:40:03PM +0530, Sunil V L wrote:
> This series improves the pflash usage in RISC-V virt machine with solutions to
> below issues.
>
> 1) Currently the first pflash is reserved for ROM/M-mode firmware code. But
> S-mode
> payload firmware like EDK2 need both pflash devices
This series improves the pflash usage in RISC-V virt machine with solutions to
below issues.
1) Currently the first pflash is reserved for ROM/M-mode firmware code. But
S-mode
payload firmware like EDK2 need both pflash devices to have separate code and
variable
store so that OS distros can keep
