From: "Dhaval Sharma" <dhaval@rivosinc.com>
To: devel@edk2.groups.io
Subject: DRAFT: [PATCH v1 0/8] RiscV64 Support In UPL
Date: Thu, 11 May 2023 12:42:18 +0530 [thread overview]
Message-ID: <20230511071226.19726-1-dhaval@rivosinc.com> (raw)
This patchset contains modifications required in UPL boot flow to
enable RiscV64 support. Squashing earlier series of patches
related to arch specific removal from UPL boot path to this release such
that all chnages can be viewed in the entirety.
1. Add required infra to support RiscV64
2. New UPL proposal supports multiple Archs and accordingly ABI
is also different. This is a proposal to accomodate these changes.
This patch adds a hook to parse RiscV64 specific IN params and extract
FDT from the same.
3. Take FDT received from BL and parse it to create required HOBs that
are later consumed by UPL.
4. Add FirmwareContext structure which is specific to RV and used by RV
CPU driver.
5. Add required modifications to extrace DxeFv from overall UPL FD.
6. Add required RV drivers to boot to UEFI Shell
P.S. This patch is review only at this point as it is tested in a limited
fashion for RV to get to early debug logs from FDT described serial device.
It will require modifications to work on other Archs.
Branch https://github.com/rivosinc/edk2/tree/upl-rv64-enable-compilation-v1
Dhaval Sharma (8):
UefiPayloadPkg: Remove FP Init from UPL entry
UefiPayloadPkg: Move INT prog outside common flow
UefiPayloadPkg: Basic Infra To Enable RV64 UPL Support
UefiPayloadPkg: Update input params as per latest UPL spec
UefiPayloadPkg: Hook to parse IN params as per UPL spec
UefiPayloadPkg: Add FirmwareContext for RV64
UefiPayloadPkg: Find DxeFV and create required FV HOB
UefiPayloadPkg: Add RV64 driver to boot to UEFI Shell
UefiPayloadPkg/UefiPayloadPkg.dsc | 2 +-
UefiPayloadPkg/{UefiPayloadPkg.dsc => UefiPayloadPkgRV64.dsc} | 448 +++-----------
UefiPayloadPkg/UefiPayloadPkgRV64.fdf | 325 ++++++++++
UefiPayloadPkg/UefiPayloadEntry/UniversalPayloadEntry.inf | 12 +-
UefiPayloadPkg/UefiPayloadEntry/Ia32/DxeLoadFunc.c | 9 +
UefiPayloadPkg/UefiPayloadEntry/Ia32/Ia32FdtParserLib.c | 33 ++
UefiPayloadPkg/UefiPayloadEntry/{X64 => RiscV64}/DxeLoadFunc.c | 62 +-
UefiPayloadPkg/UefiPayloadEntry/RiscV64/Rv64FdtParserLib.c | 625 ++++++++++++++++++++
UefiPayloadPkg/UefiPayloadEntry/UniversalPayloadEntry.c | 29 +-
UefiPayloadPkg/UefiPayloadEntry/X64/DxeLoadFunc.c | 9 +
UefiPayloadPkg/UefiPayloadEntry/X64/X64FdtParserLib.c | 33 ++
11 files changed, 1166 insertions(+), 421 deletions(-)
copy UefiPayloadPkg/{UefiPayloadPkg.dsc => UefiPayloadPkgRV64.dsc} (63%)
create mode 100644 UefiPayloadPkg/UefiPayloadPkgRV64.fdf
create mode 100644 UefiPayloadPkg/UefiPayloadEntry/Ia32/Ia32FdtParserLib.c
copy UefiPayloadPkg/UefiPayloadEntry/{X64 => RiscV64}/DxeLoadFunc.c (51%)
create mode 100644 UefiPayloadPkg/UefiPayloadEntry/RiscV64/Rv64FdtParserLib.c
create mode 100644 UefiPayloadPkg/UefiPayloadEntry/X64/X64FdtParserLib.c
--
2.34.1
next reply other threads:[~2023-05-11 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 7:12 Dhaval Sharma [this message]
2023-05-11 7:12 ` [PATCH v1 1/8] UefiPayloadPkg: Remove FP Init from UPL entry Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 2/8] UefiPayloadPkg: Move INT prog outside common flow Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 3/8] UefiPayloadPkg: Basic Infra To Enable RV64 UPL Support Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 4/8] UefiPayloadPkg: Update input params as per latest UPL spec Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 5/8] UefiPayloadPkg: Hook to parse IN params as per " Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 6/8] UefiPayloadPkg: Add FirmwareContext for RV64 Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 7/8] UefiPayloadPkg: Find DxeFV and create required FV HOB Dhaval Sharma
2023-05-11 7:12 ` [PATCH v1 8/8] UefiPayloadPkg: Add RV64 driver to boot to UEFI Shell Dhaval Sharma
-- strict thread matches above, loose matches on Subject: below --
2023-05-11 7:08 DRAFT: [PATCH v1 0/8] RiscV64 Support In UPL Dhaval Sharma
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=20230511071226.19726-1-dhaval@rivosinc.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