From: "Abner Chang" <abner.chang@hpe.com>
To: Leif Lindholm <leif@nuviainc.com>,
"Schaefer, Daniel (DualStudy)" <daniel.schaefer@hpe.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Chen, Gilbert" <gilbert.chen@hpe.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [platform/devel-riscvplatforms PATCHv1 0/2] New RISC-V patches
Date: Tue, 12 May 2020 00:38:23 +0000 [thread overview]
Message-ID: <TU4PR8401MB04293AC73208B2783D10E73DFFBE0@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20200511173857.GV21486@vanye>
> -----Original Message-----
> From: Leif Lindholm [mailto:leif@nuviainc.com]
> Sent: Tuesday, May 12, 2020 1:39 AM
> To: Schaefer, Daniel (DualStudy) <daniel.schaefer@hpe.com>
> Cc: devel@edk2.groups.io; Chen, Gilbert <gilbert.chen@hpe.com>; Chang,
> Abner (HPS SW/FW Technologist) <abner.chang@hpe.com>; Michael D
> Kinney <michael.d.kinney@intel.com>
> Subject: Re: [platform/devel-riscvplatforms PATCHv1 0/2] New RISC-V
> patches
>
> On Mon, May 11, 2020 at 19:20:13 +0200, Daniel Schaefer wrote:
> > We have moved most of our RISC-V implementation to edk2-platforms
> now,
> > only the absolute minimum is in edk2, already merged.
> > All other patches going into edk2-platforms have already been merged,
> these are new.
>
> Please be explicit on what has been merged to edk2/edk2-platforms and
> what has been merged to edk2-staging/edk2-platforms-devel.
Daniel, we can mention this in cover letter.
>
> > The first adds opensbi as a submodule. We wanted to have it reviewed
> > because it would be the first submodule in the edk2-platforms repository.
> Is that okay?
>
> I have no objection to submodules in edk2-platforms, although this will be
> the first one. Just remember to call this out explicitly in any instructions.
Daniel, we can add Submodule section in Readme.md which as same as the readme under edk2.
>
> /
> Leif
>
> > Since we are now running PEI in addition to DXE in S-Mode (like Ring 3
> > in x86), we need to call into the SBI interface. The new library
> > provides an interface for EDK2 code to do that. It just wraps the
> > ecall assembly instruction as a C interface with EDK2-style return codes.
> >
> > Cc: Gilbert Chen <gilbert.chen@hpe.com>
> > Cc: Abner Chang <abner.chang@hpe.com>
> > Cc: Leif Lindholm <leif@nuviainc.com>
> > Cc: Michael D Kinney <michael.d.kinney@intel.com>
> >
> > Daniel Schaefer (2):
> > ProcessorPkg/RiscVOpensbLlib: Add submodule opensbi
> > ProcessorPkg/Library: Add EDK2 RISC-V OpenSBI library.
> >
> > Silicon/RISC-V/ProcessorPkg/Library/RiscVOpensbiLib/RiscVOpensbiLib.inf
> | 60 +++++++++++++++
> > Silicon/RISC-V/ProcessorPkg/Include/IndustryStandard/RiscVOpensbi.h
> | 79 ++++++++++++++++++++
> > Silicon/RISC-V/ProcessorPkg/Include/OpensbiTypes.h | 66
> ++++++++++++++++
> > .gitmodules | 3 +
> > Silicon/RISC-V/ProcessorPkg/Library/RiscVOpensbiLib/opensbi | 1 +
> > 5 files changed, 209 insertions(+)
> > create mode 100644
> > Silicon/RISC-V/ProcessorPkg/Library/RiscVOpensbiLib/RiscVOpensbiLib.in
> > f create mode 100644
> > Silicon/RISC-V/ProcessorPkg/Include/IndustryStandard/RiscVOpensbi.h
> > create mode 100644 Silicon/RISC-V/ProcessorPkg/Include/OpensbiTypes.h
> > create mode 100644 .gitmodules
> > create mode 160000
> > Silicon/RISC-V/ProcessorPkg/Library/RiscVOpensbiLib/opensbi
> >
> > --
> > 2.26.1
> >
prev parent reply other threads:[~2020-05-12 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 17:20 [platform/devel-riscvplatforms PATCHv1 0/2] New RISC-V patches Daniel Schaefer
2020-05-11 17:20 ` [platform/devel-riscvplatforms PATCHv1 1/2] ProcessorPkg/RiscVOpensbLlib: Add submodule opensbi Daniel Schaefer
2020-05-11 17:20 ` [platform/devel-riscvplatforms PATCHv1 2/2] ProcessorPkg/Library: Add EDK2 RISC-V OpenSBI library Daniel Schaefer
2020-05-11 23:17 ` [edk2-devel] " Leif Lindholm
2020-05-15 13:38 ` Daniel Schaefer
2020-05-11 17:38 ` [platform/devel-riscvplatforms PATCHv1 0/2] New RISC-V patches Leif Lindholm
2020-05-12 0:38 ` Abner Chang [this message]
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=TU4PR8401MB04293AC73208B2783D10E73DFFBE0@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.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