[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ede95b25bb1e27ccfd1380896b5b8ec055184f2c.camel@wdc.com>
Date: Thu, 21 Nov 2019 19:07:20 +0000
From: Atish Patra <Atish.Patra@....com>
To: "paul.walmsley@...ive.com" <paul.walmsley@...ive.com>
CC: "linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"hch@....de" <hch@....de>, "han_mao@...ky.com" <han_mao@...ky.com>,
"gary@...yguo.net" <gary@...yguo.net>,
"rppt@...ux.ibm.com" <rppt@...ux.ibm.com>,
"palmer@...belt.com" <palmer@...belt.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"allison@...utok.net" <allison@...utok.net>,
"behrensj@....edu" <behrensj@....edu>,
"anup@...infault.org" <anup@...infault.org>,
"alexios.zavras@...el.com" <alexios.zavras@...el.com>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>
Subject: Re: [PATCH v3 0/4] Add support for SBI v0.2
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
Powered by blists - more mailing lists