From: "Sunil V L" <sunilvl@ventanamicro.com>
To: devel@edk2.groups.io
Cc: Sunil V L <sunilvl@ventanamicro.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Andrei Warkentin <andrei.warkentin@intel.com>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Dann Frazier <dann.frazier@canonical.com>
Subject: [PATCH v3 0/4] OvmfPkg/RiscVVirt: Separate code and variable storage
Date: Tue, 20 Jun 2023 15:32:40 +0530 [thread overview]
Message-ID: <20230620100244.1404606-1-sunilvl@ventanamicro.com> (raw)
Recent updates to RISC-V qemu virt platform merged today (07/14),
have enabled both pflash devices for the S-mode payload like EDK2.
These updates also aligned the design similar to other architectures
where pflash0 is for read-only code and pflash1 for variable store.
Previously only pflash1 was available for S-mode use.
Current EDK2 will not work with this latest qemu changes since it always
assumed to boot from pflash1. So, separate the code and variable
store and use pflash0 to keep the code.
Add 'readme' about build and test as per these changes.
The changes are available in the branch :
https://github.com/vlsunil/edk2/tree/separate_code_vars
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Andrei Warkentin <andrei.warkentin@intel.com>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Dann Frazier <dann.frazier@canonical.com>
Changes since v2:
1) Addressed Heinrich's comments in readme.
Changes since v1:
1) Updated readme to add minimum qemu version required.
Sunil V L (4):
OvmfPkg/RiscVVirt: Fix couple of issues in VarStore
OvmfPkg/RiscVVirt: Add VirtNorFlashDeviceTreeLib library
OvmfPkg/RiscVVirt: Add support for separate code and variable store
OvmfPkg/RiscVVirt: Add a readme for build and test
OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc | 2 +-
OvmfPkg/RiscVVirt/RiscVVirtQemu.fdf | 16 +-
.../VirtNorFlashDeviceTreeLib.inf | 40 +++++
.../VirtNorFlashDeviceTreeLib.c | 137 ++++++++++++++++++
OvmfPkg/RiscVVirt/README.md | 49 +++++++
OvmfPkg/RiscVVirt/RiscVVirt.fdf.inc | 14 +-
OvmfPkg/RiscVVirt/VarStore.fdf.inc | 12 +-
7 files changed, 251 insertions(+), 19 deletions(-)
create mode 100644 OvmfPkg/RiscVVirt/Library/VirtNorFlashPlatformLib/VirtNorFlashDeviceTreeLib.inf
create mode 100644 OvmfPkg/RiscVVirt/Library/VirtNorFlashPlatformLib/VirtNorFlashDeviceTreeLib.c
create mode 100644 OvmfPkg/RiscVVirt/README.md
--
2.34.1
next reply other threads:[~2023-06-20 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:02 Sunil V L [this message]
2023-06-20 10:02 ` [PATCH v3 1/4] OvmfPkg/RiscVVirt: Fix couple of issues in VarStore Sunil V L
2023-06-20 10:02 ` [PATCH v3 2/4] OvmfPkg/RiscVVirt: Add VirtNorFlashDeviceTreeLib library Sunil V L
2023-06-20 10:02 ` [PATCH v3 3/4] OvmfPkg/RiscVVirt: Add support for separate code and variable store Sunil V L
2023-06-20 10:02 ` [PATCH v3 4/4] OvmfPkg/RiscVVirt: Add a readme for build and test Sunil V L
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230620100244.1404606-1-sunilvl@ventanamicro.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox