From: Jessica Clarke <jrtc27@jrtc27.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] riscv: default to CONFIG_RISCV_SBI_V01=n
Date: Thu, 16 Dec 2021 16:51:28 +0000 [thread overview]
Message-ID: <150C4E84-2C69-45DB-AF27-1E0C223D8D7A@jrtc27.com> (raw)
In-Reply-To: <fd40010f-f2ec-b32a-6850-1e054af43725@canonical.com>
On 16 Dec 2021, at 14:17, Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:
>
> On 12/16/21 14:49, Jessica Clarke wrote:
>> On 16 Dec 2021, at 12:35, Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:
>>>
>>> The SBI 0.1 specification is obsolete. The current version is 0.3.
>>> Hence we should not rely by default on SBI 0.1 being implemented.
>> It’s what BBL implements, and some people are still using it,
>> especially given early hardware shipped before OpenSBI grew in
>> popularity.
>> Jess
>
> Do you mean BBL is not developed anymore?
>
> Some people may still be using a 0.1 SBI. But that minority stuck on an outdated software stack does not justify defaulting to deprecated settings in future Linux releases.
BBL is still actively maintained; its most recent commit was 24 days
ago. Also, the amount of code CONFIG_RISCV_SBI_V01 affects is tiny, so
I see no tangible benefit from making this change, just unnecessary
breakage of perfectly functional systems.
Jess
next prev parent reply other threads:[~2021-12-16 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 12:35 Heinrich Schuchardt
2021-12-16 13:49 ` Jessica Clarke
2021-12-16 14:17 ` Heinrich Schuchardt
2021-12-16 16:51 ` Jessica Clarke [this message]
2021-12-17 10:42 ` Heinrich Schuchardt
2021-12-17 12:09 ` Anup Patel
2021-12-17 18:35 ` Palmer Dabbelt
2022-01-20 16:58 ` Palmer Dabbelt
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=150C4E84-2C69-45DB-AF27-1E0C223D8D7A@jrtc27.com \
--to=jrtc27@jrtc27.com \
--cc=aou@eecs.berkeley.edu \
--cc=heinrich.schuchardt@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®