From: Marcus Comstedt <marcus@mc.pp.se>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] clk: sifive: Fix ethernet regression on HiFive Unleashed
Date: Mon, 09 Sep 2019 22:52:09 +0200 [thread overview]
Message-ID: <yf9a7bdxkee.fsf@mc.pp.se> (raw)
In-Reply-To: <CAEUhbmXTe2pLpuUT8aOFT9ZytVC0RgDB=wQzHtQvj=tAghL7Ug@mail.gmail.com> (Bin Meng's message of "Mon, 9 Sep 2019 10:50:12 +0800")
Hi Bin,
Bin Meng <bmeng.cn@gmail.com> writes:
>> Yes, but in which Linux? This whole thing started because U-Boot will
>
> The latest Linux kernel v5.3.
Thanks. I'll try it later. As if to prove my point, the one from
5.2.11 (which is the Linux version I'm currently running) did not work
(I got MMC but no ethernet)...
> I checked kernel 4.14 and found it did not ship the SiFive Unleased
> board DTS in the kernel tree. Are you sure it's 4.14?
It's the one shipped with the H5U, which I'm pretty sure ran Linux
4.14 at the time (as part of the "Freedom U SDK") since 4.15 was not
out yet. It looks like SiFive never added the DTS to their own Linux
tree (https://github.com/sifive/riscv-linux).
> I don't think Linux is to be blamed for this case. They have a policy
> to maintain the the backward compatibility for the DT land. The issue
> what you were facing here is an out of tree DTB (the vendors') is
> incompatible with the kernel's. Once the kernel accepts a DTS,
> bringing in any out-of-tree DT with changes reviewed to in-tree,
> future compatibility will be assured.
Isn't the reason that the DTS accepted by the kernel is different from
the out-of-tree vendor one that the review process caused changes in
the DTS then? It seems unlikely that the vendor (SiFive) would
deliberately submit an incompatible DTS for inclusion...
// Marcus
next prev parent reply other threads:[~2019-09-09 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 9:35 [U-Boot] [PATCH] clk: sifive: Fix ethernet regression on HiFive Unleashed Marcus Comstedt
2019-09-08 12:38 ` Bin Meng
2019-09-08 12:54 ` Marcus Comstedt
2019-09-08 12:58 ` Bin Meng
2019-09-08 13:19 ` Marcus Comstedt
2019-09-08 13:49 ` Bin Meng
2019-09-08 14:48 ` Marcus Comstedt
2019-09-09 2:50 ` Bin Meng
2019-09-09 20:52 ` Marcus Comstedt [this message]
2019-09-10 15:20 ` Bin Meng
2019-09-10 15:53 ` Marcus Comstedt
2019-09-11 1:58 ` Bin Meng
2019-09-11 6:24 ` Anup Patel
2019-09-11 7:43 ` Bin Meng
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=yf9a7bdxkee.fsf@mc.pp.se \
--to=marcus@mc.pp.se \
--cc=u-boot@lists.denx.de \
/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