public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Sun, 08 Sep 2019 16:48:37 +0200	[thread overview]
Message-ID: <yf9v9u2j12y.fsf@mc.pp.se> (raw)
In-Reply-To: <CAEUhbmURUFfk6Hg_si-bAKQzDmEt_rJ+jUPy-4HB0=q_hZzUBQ@mail.gmail.com> (Bin Meng's message of "Sun, 8 Sep 2019 21:49:40 +0800")


Hi Bin,

Bin Meng <bmeng.cn@gmail.com> writes:

>> And which "Linux DTB" should that be?  Since RISC-V seems to be going
>
> The one in arch/riscv/boot/dts/sifive.

Yes, but in which Linux?  This whole thing started because U-Boot will
no longer accept the DTB used with Linux 4.14.  If each Linux version is
going to have its own incompatible DTB then U-Boot either needs to
decide which one to work with, or work with the vendor DTB (which
would be perferable in my opinion).


> As for the syntax of the nodes keep changing, I would say that's
> inevitable because of the upstreaming process. Everything in vendor's
> DT that does not get merged in Linux will remain potentially changed
> by later upstreaming reviews.

An upstreaming review that suggests changing a driver so that it no
longer works with the vendor's DTB is IMHO contraproductive and
against the very idea of DTB, but I suppose there's little that can be
done to affect the review process over at Linux land...  It would be
nice if this weirdness did not spill over on U-Boot/OpenSBI though.


  // Marcus

  reply	other threads:[~2019-09-08 14:48 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 [this message]
2019-09-09  2:50             ` Bin Meng
2019-09-09 20:52               ` Marcus Comstedt
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=yf9v9u2j12y.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