From: Paul Walmsley <paul.walmsley@sifive.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Atish Patra <atish.patra@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART
Date: Fri, 3 May 2019 12:05:09 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1905031141530.4777@viisi.sifive.com> (raw)
In-Reply-To: <7hsgtwlm5t.fsf@baylibre.com>
On Thu, 2 May 2019, Kevin Hilman wrote:
> Paul Walmsley <paul.walmsley@sifive.com> writes:
>
> > I'd recommend testing the DT patches with BBL and the open-source FSBL.
> > That's the traditional way of booting RISC-V Linux systems.
>
> OK, but as you know, not the tradiaional way of booting most other linux
> systems. ;)
>
> I'm working on getting RISC-V supported in kernelCI in a fully-automated
> way, and I don't currently have the time to add add support for BBL+FSBL
> to kernelCI automation tooling, so having u-boot support is the best way
> to get support in kernelCI, IMO.
That's great. Please keep hacking away on RISC-V support for kernelCI.
My point is just that the U-boot and OpenSBI software stack you're working
with is not going to be useful for automatic tests of some kernel patches
yet. That stack is still very new, and was written around a non-upstream
set of DT data. We are in the process of posting and merging patches to
fix that, but it's going to take a few releases of both the kernel and
those other boot stack components until things are sorted out in a more
durable way.
- Paul
next prev parent reply other threads:[~2019-05-03 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 2:01 [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART Paul Walmsley
2019-04-13 2:01 ` [PATCH v5 1/2] dt-bindings: serial: add documentation for the SiFive UART driver Paul Walmsley
2019-04-26 14:08 ` Rob Herring
2019-04-26 16:36 ` Paul Walmsley
2019-04-13 2:01 ` [PATCH v5 2/2] tty: serial: add driver for the SiFive UART Paul Walmsley
2019-05-02 18:58 ` Kevin Hilman
2019-04-18 23:22 ` [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART Kevin Hilman
2019-04-19 1:04 ` Atish Patra
2019-04-19 19:18 ` Kevin Hilman
2019-04-19 19:29 ` Atish Patra
2019-04-19 20:34 ` Kevin Hilman
2019-04-19 21:13 ` Paul Walmsley
2019-05-02 18:57 ` Kevin Hilman
2019-05-03 19:05 ` Paul Walmsley [this message]
2019-04-24 18:58 ` Paul Walmsley
2019-05-27 16:12 ` Loys Ollivier
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=alpine.DEB.2.21.9999.1905031141530.4777@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=atish.patra@wdc.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.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 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).