From: Troy Benjegerdes <troy.benjegerdes@sifive.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: anup.patel@wdc.com, "Atish Patra" <atish.patra@wdc.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Björn Töpel" <bjorn.topel@gmail.com>
Subject: Re: 5.2-rc1 boot on Unleashed
Date: Thu, 23 May 2019 19:23:40 -0500 [thread overview]
Message-ID: <8F4FB234-FD5B-4AD6-99BD-57A40A79A024@sifive.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1905221334460.23235@viisi.sifive.com>
> On May 22, 2019, at 3:43 PM, Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> + Anup, Troy
>
> On Wed, 22 May 2019, Atish Patra wrote:
>
>> On 5/22/19 9:42 AM, Paul Walmsley wrote:
>>> Am checking on this now and hope to have some conclusion on it this week.
>>
>> Thanks. Any chance you can take a look at the U-Boot clock driver to patch it
>> as per the DT changes ?
>
> I probably won't have the chance to get to it for a while. Looks like
> Anup was the one who posted the clock driver to U-Boot - can he take a
> look at it?
>
> We've also asked Troy to look at upstream U-boot related issues, but
> I'm unsure when patches will start flowing upstream.
>
>
> - Paul
I’d prefer to hold off on any changes to U-boot until we have a more complete patch set. GPIO and ethernet entries are missing from those device trees, and we have a working U-boot device tree now. If the kernel needs something different we can load the device tree the kernel needs for awhile.
The U-boot device tree is going to have some things in it the kernel doesn’t care about anyway, so we’ve already got divergence between the two. Ideally the U-boot version is a superset of the kernel version. We already had one disruptive change with the clock driver, so what is to prevent there to be more disruptive changes in the ethernet/GPIO device tree entries that go in the kernel unless we have a draft of what those entries should look like that is acceptable?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-24 0:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 23:31 5.2-rc1 boot on Unleashed Atish Patra
2019-05-21 9:40 ` Andreas Schwab
2019-05-21 18:14 ` Atish Patra
2019-05-22 7:31 ` Andreas Schwab
2019-05-22 8:40 ` Andreas Schwab
2019-05-22 9:58 ` Andreas Schwab
2019-05-22 21:13 ` Paul Walmsley
2019-05-21 17:47 ` Kevin Hilman
2019-05-21 18:18 ` Atish Patra
2019-05-23 9:42 ` Andreas Schwab
2019-05-22 4:42 ` Sagar Kadam
2019-05-22 9:51 ` Atish Patra
2019-05-22 16:42 ` Paul Walmsley
2019-05-22 17:38 ` Atish Patra
2019-05-22 20:43 ` Paul Walmsley
2019-05-22 22:14 ` Troy Benjegerdes
2019-05-25 8:06 ` Anup Patel
2019-05-25 14:16 ` Troy Benjegerdes
2019-05-29 5:00 ` Anup Patel
2019-05-29 8:31 ` Andreas Schwab
2019-05-29 17:38 ` Troy Benjegerdes
2019-05-29 18:59 ` Karsten Merker
2019-05-30 17:00 ` Palmer Dabbelt
2019-06-03 10:49 ` Andreas Schwab
2019-06-03 14:44 ` Distro bootcmd: " Troy Benjegerdes
2019-06-03 17:02 ` [U-Boot] " Tom Rini
2019-06-03 19:17 ` Palmer Dabbelt
2019-06-03 19:32 ` Tom Rini
2019-06-03 19:47 ` Troy Benjegerdes
2019-05-24 0:23 ` Troy Benjegerdes [this message]
2019-05-24 3:59 ` Atish Patra
2019-05-24 14:46 ` Troy Benjegerdes
2019-05-24 15:35 ` Auer, Lukas
2019-05-24 16:01 ` Troy Benjegerdes
2019-05-24 17:40 ` Atish Patra
[not found] ` <CAF5mof3_PSwpsSMnjMALpfvmOPdeAgDLa2p6jp4y+Hmas83mbw@mail.gmail.com>
2019-05-24 21:34 ` Auer, Lukas
2019-05-25 3:49 ` Anup Patel
2019-05-25 16:23 ` Troy Benjegerdes
2019-05-25 18:09 ` Paul Walmsley
2019-05-25 18:40 ` Troy Benjegerdes
2019-05-27 12:21 ` Andreas Schwab
2019-05-27 16:51 ` Troy Benjegerdes
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=8F4FB234-FD5B-4AD6-99BD-57A40A79A024@sifive.com \
--to=troy.benjegerdes@sifive.com \
--cc=anup.patel@wdc.com \
--cc=atish.patra@wdc.com \
--cc=bjorn.topel@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--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;
as well as URLs for NNTP newsgroup(s).