All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: j.neuschaefer@gmx.net
Cc: robh@kernel.org, j.neuschaefer@gmx.net, mark.rutland@arm.com,
	devicetree@vger.kernel.org, patches@groups.riscv.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patches] Re: [PATCH] dt-bindings: Add a RISC-V SBI firmware node
Date: Tue, 21 Nov 2017 16:36:22 -0800 (PST)	[thread overview]
Message-ID: <mhng-40a689c5-fa7b-4cff-9739-555b7c65981f@palmer-si-x1c4> (raw)
In-Reply-To: <20171121200832.d55khzcufo2owcff@latitude>

On Tue, 21 Nov 2017 12:08:32 PST (-0800), 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.)
>
>> 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.

OK, sounds good!

WARNING: multiple messages have this Message-ID (diff)
From: 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 16:36:22 -0800 (PST)	[thread overview]
Message-ID: <mhng-40a689c5-fa7b-4cff-9739-555b7c65981f@palmer-si-x1c4> (raw)
In-Reply-To: <20171121200832.d55khzcufo2owcff@latitude>

On Tue, 21 Nov 2017 12:08:32 PST (-0800), j.neuschaefer-hi6Y0CQ0nG0@public.gmane.org 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.)
>
>> 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.

OK, sounds good!
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-11-22  0:36 UTC|newest]

Thread overview: 19+ 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
2017-11-20 19:50 ` Palmer Dabbelt
2017-11-20 20:28 ` Jonathan Neuschäfer
2017-11-20 20:28   ` Jonathan Neuschäfer
2017-11-20 21:28   ` [patches] " Palmer Dabbelt
2017-11-20 21:28     ` Palmer Dabbelt
2017-11-21  1:08     ` Jonathan Neuschäfer
2017-11-21  1:08       ` Jonathan Neuschäfer
2017-11-21 17:41       ` Palmer Dabbelt
2017-11-21 17:41         ` Palmer Dabbelt
2017-11-21 10:43     ` Mark Rutland
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-21 20:08       ` Jonathan Neuschäfer
2017-11-22  0:36       ` Palmer Dabbelt [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=mhng-40a689c5-fa7b-4cff-9739-555b7c65981f@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=patches@groups.riscv.org \
    --cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.