From: Atish Patra <Atish.Patra@wdc.com>
To: "paul.walmsley@sifive.com" <paul.walmsley@sifive.com>
Cc: "aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"anup@brainfault.org" <anup@brainfault.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rppt@linux.ibm.com" <rppt@linux.ibm.com>,
"alexios.zavras@intel.com" <alexios.zavras@intel.com>,
"behrensj@mit.edu" <behrensj@mit.edu>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"allison@lohutok.net" <allison@lohutok.net>,
"gary@garyguo.net" <gary@garyguo.net>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>, "hch@lst.de" <hch@lst.de>,
"han_mao@c-sky.com" <han_mao@c-sky.com>
Subject: Re: [PATCH v3 0/4] Add support for SBI v0.2
Date: Thu, 21 Nov 2019 19:07:20 +0000 [thread overview]
Message-ID: <ede95b25bb1e27ccfd1380896b5b8ec055184f2c.camel@wdc.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1911192344560.12489@viisi.sifive.com>
On Tue, 2019-11-19 at 23:51 -0800, Paul Walmsley wrote:
> Hi Atish,
>
> On Mon, 18 Nov 2019, Atish Patra wrote:
>
> > The Supervisor Binary Interface(SBI) specification[1] now defines a
> > base extension that provides extendability to add future extensions
> > while maintaining backward compatibility with previous versions.
> > The new version is defined as 0.2 and older version is marked as
> > 0.1.
> >
> > This series adds support v0.2 and a unified calling convention
> > implementation between 0.1 and 0.2. It also adds minimal SBI
> > functions
> > from 0.2 as well to keep the series lean.
> >
> > [1]
> > https://github.com/riscv/riscv-sbi-doc/blob/master/riscv-sbi.adoc
> >
> > The base support for SBI v0.2 is already available in OpenSBI v0.5.
> > This series needs following additional patches in OpenSBI.
> >
> > http://lists.infradead.org/pipermail/opensbi/2019-November/000704.html
> >
> > Tested on both BBL, OpenSBI with/without the above patch series.
>
> Just based on a quick look:
>
> All of the patches in this series add warnings reported by
> 'scripts/checkpatch.pl --strict'. Could you please fix and repost?
>
Yeah sure. I will do that.
> Also: could you rebase these patches on top of the current RISC-V
> for-next
> branch? There are some significant conflicts after Christoph's
> nommu
> work.
>
ok. I will rebase on top of for-next.
> We'll wait to send these upstream until the SBI v0.2 spec is frozen,
> but
> in the meantime, it'll be good to get these into the experimental
> branch.
>
> thanks,
>
> - Paul
--
Regards,
Atish
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-11-21 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 22:45 [PATCH v3 0/4] Add support for SBI v0.2 Atish Patra
2019-11-18 22:45 ` [PATCH v3 1/4] RISC-V: Mark existing SBI as 0.1 SBI Atish Patra
2019-11-18 22:45 ` [PATCH v3 2/4] RISC-V: Add basic support for SBI v0.2 Atish Patra
2019-11-18 22:45 ` [PATCH v3 3/4] RISC-V: Introduce a new config for SBI v0.1 Atish Patra
2019-11-18 22:45 ` [PATCH v3 4/4] RISC-V: Implement SBI v0.2 replacement extensions Atish Patra
2019-11-20 7:51 ` [PATCH v3 0/4] Add support for SBI v0.2 Paul Walmsley
2019-11-21 19:07 ` Atish Patra [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-all 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=ede95b25bb1e27ccfd1380896b5b8ec055184f2c.camel@wdc.com \
--to=atish.patra@wdc.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=behrensj@mit.edu \
--cc=gary@garyguo.net \
--cc=han_mao@c-sky.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).