From: "Jonathan Neuschäfer" <j.neuschaefer-hi6Y0CQ0nG0@public.gmane.org>
To: Palmer Dabbelt <palmer-SpMDHPYPyPbQT0dZR+AlfA@public.gmane.org>
Cc: robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
j.neuschaefer-hi6Y0CQ0nG0@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
patches-q3qR2WxjNRFS9aJRtSZj7A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patches] Re: [PATCH] dt-bindings: Add a RISC-V SBI firmware node
Date: Tue, 21 Nov 2017 21:08:32 +0100 [thread overview]
Message-ID: <20171121200832.d55khzcufo2owcff@latitude> (raw)
In-Reply-To: <mhng-dadf76d9-0823-4fc8-9177-1772629573b6@palmer-si-x1c4>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
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.)
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-11-21 20:08 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 [this message]
2017-11-22 0:36 ` Palmer Dabbelt
2017-11-28 19:43 ` Rob Herring
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=20171121200832.d55khzcufo2owcff@latitude \
--to=j.neuschaefer-hi6y0cq0ng0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=palmer-SpMDHPYPyPbQT0dZR+AlfA@public.gmane.org \
--cc=patches-q3qR2WxjNRFS9aJRtSZj7A@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).