From: Andreas Schwab <schwab@suse.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Working device tree for the HifiveU
Date: Mon, 17 Jun 2019 14:11:35 +0200 [thread overview]
Message-ID: <mvmd0jc5s3s.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906170347460.19994@viisi.sifive.com> (Paul Walmsley's message of "Mon, 17 Jun 2019 03:58:46 -0700 (PDT)")
On Jun 17 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> On Mon, 17 Jun 2019, Andreas Schwab wrote:
>
>> What is the correct device tree for the HifiveU that works both with
>> 5.2+ and U-Boot?
>
> U-Boot should follow the kernel's DT data:
>
> http://git.denx.de/?p=u-boot.git;a=blob;f=doc/device-tree-bindings/README;h=2ea3439a170236bd912930991ad70ee7289dcd29;hb=HEAD
>
> Thus the upstream-bound data is currently here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
>
> However, since some FU540 U-Boot drivers were upstreamed before the kernel
> DT data was posted and reviewed, it's necessary to patch upstream U-Boot
> to use the upstream-bound DT data format. One of the patches required can
> be found here:
>
> https://lists.denx.de/pipermail/u-boot/2019-May/370814.html
Any patch to make serial work again?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-06-17 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 10:14 Working device tree for the HifiveU Andreas Schwab
2019-06-17 10:58 ` Paul Walmsley
2019-06-17 12:11 ` Andreas Schwab [this message]
2019-06-17 12:19 ` Andreas Schwab
2019-06-17 12:47 ` Paul Walmsley
2019-06-17 12:49 ` Andreas Schwab
2019-06-17 13:21 ` Troy Benjegerdes
2019-06-17 13:31 ` Paul Walmsley
2019-06-17 13:35 ` Troy Benjegerdes
2019-06-17 13:41 ` Paul Walmsley
2019-06-17 13:50 ` Andreas Schwab
2019-06-17 13:26 ` Paul Walmsley
2019-06-17 13:28 ` Andreas Schwab
2019-06-17 13:34 ` Paul Walmsley
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=mvmd0jc5s3s.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-riscv@lists.infradead.org \
--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