[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1908061818360.13971@viisi.sifive.com>
Date: Tue, 6 Aug 2019 18:26:08 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Atish Patra <Atish.Patra@....com>
cc: "info@...ux.net" <info@...ux.net>,
"allison@...utok.net" <allison@...utok.net>,
"palmer@...ive.com" <palmer@...ive.com>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
Anup Patel <Anup.Patel@....com>,
"mark.rutland@....com" <mark.rutland@....com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"johan@...nel.org" <johan@...nel.org>,
"tiny.windzz@...il.com" <tiny.windzz@...il.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"gary@...yguo.net" <gary@...yguo.net>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH v3 3/5] RISC-V: Fix unsupported isa string info.
On Wed, 7 Aug 2019, Atish Patra wrote:
> On Tue, 2019-08-06 at 16:27 -0700, Paul Walmsley wrote:
>
> > Seems like the "su" should be dropped from mandatory_ext. What do you
> > think?
> >
>
> Yup. As DT binding only mention imafdc, mandatory extensions should
> contain only that and just consider "su" extensions are considered as
> implicit as we are running Linux.
Discussing this with Andrew and Palmer, it looks like "su" is currently
non-compliant. Section 22.6 of the user-level specification states that
the "s" character indicates that a longer standard supervisor extension
name will follow. So far I don't think any of these have been defined.
> Do you think QEMU DT should be updated to reflect that ?
Yes.
> > There's no Kconfig option by this name, and we're requiring
> > compressed
>
> Sorry. This was a typo. It should have been CONFIG_RISCV_ISA_C.
>
> > instruction support as part of the RISC-V Linux baseline. Could you
> > share the rationale behind this?
>
> I think I added this check at the config file. Looking at the Kconfig,
> RISCV_ISA_C is always enabled. So we can drop this.
OK great. Do you want to resend an updated patch, or would you like me to
fix it up here?
I'll also send a patch to drop CONFIG_RISCV_ISA_C.
- Paul
Powered by blists - more mailing lists