From: Rob Herring <robh@kernel.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: Palmer Dabbelt <palmer@sifive.com>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
patches@groups.riscv.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [patches] Re: [PATCH] dt-bindings: Add a RISC-V SBI firmware node
Date: Tue, 28 Nov 2017 13:43:00 -0600 [thread overview]
Message-ID: <CAL_JsqL9XSVCgouCftMfm3FQCPgg6S2775JJ_7HhxBxqDBnB-Q@mail.gmail.com> (raw)
In-Reply-To: <20171121200832.d55khzcufo2owcff@latitude>
On Tue, Nov 21, 2017 at 2:08 PM, Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> On Tue, Nov 21, 2017 at 09:37:02AM -0800, Palmer Dabbelt wrote:
> [...]
>> This isn't really a big deal to me, as I'm only interested in RISC-V
>> systems, but there's been some pushback on the concept of an SBI so it
>> seemed like a simple way to allow people to build non-SBI (and there for not
>> really RISC-V) systems.
>
> For those reading along: I suggested the /firmware/sbi node to Palmer,
> because I'm interested in such "not really RISC-V" systems, (because it
> makes the firmware's job easier to not implement the SBI — speaking with
> my coreboot hat, here.)
Seems some property to signify "not really RISC-V" would be better than adding a node for all conformant systems. If this is just one
>
>> One option that wouldn't require a device tree node
>> would be to have Linux boot in machine mode [...] and then provide its
>> own SBI implementation.
>
> I think this can work.
>
>
> Thanks,
> Jonathan Neuschäfer
prev parent reply other threads:[~2017-11-28 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 19:50 [PATCH] dt-bindings: Add a RISC-V SBI firmware node Palmer Dabbelt
[not found] ` <20171120195000.2070-1-palmer-SpMDHPYPyPbQT0dZR+AlfA@public.gmane.org>
2017-11-20 20:28 ` Jonathan Neuschäfer
2017-11-20 21:28 ` [patches] " Palmer Dabbelt
2017-11-21 1:08 ` Jonathan Neuschäfer
2017-11-21 17:41 ` Palmer Dabbelt
2017-11-21 10:43 ` Mark Rutland
2017-11-20 21:45 ` Rob Herring
2017-11-21 17:37 ` [patches] " Palmer Dabbelt
2017-11-21 20:08 ` Jonathan Neuschäfer
2017-11-22 0:36 ` Palmer Dabbelt
2017-11-28 19:43 ` Rob Herring [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=CAL_JsqL9XSVCgouCftMfm3FQCPgg6S2775JJ_7HhxBxqDBnB-Q@mail.gmail.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
/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).