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 15:19:06 +0200	[thread overview]
Message-ID: <yf98sqzj585.fsf@mc.pp.se> (raw)
In-Reply-To: <CAEUhbmW0i-JQh9zBxbM=8GuTQ5dHH2coA+H_fGeDpGipx5egtQ@mail.gmail.com> (Bin Meng's message of "Sun, 8 Sep 2019 20:58:46 +0800")


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

> OpenSBI v0.4 works fine if you supply the the Linux DTB via
> FW_PAYLOAD_FDT_PATH when building OpenSBI.

And which "Linux DTB" should that be?  Since RISC-V seems to be going
the same annoying way as ARM with a requirement that you switch DTB
every time you switch kernel version even though the hardware the DTB
describes stays the same, because the syntax of the nodes keep
changing, it's necessary to decide on a specific firmware DTB which is
decoupled from the Linux DTB (which can be loaded separately from
U-Boot as long as the ethernet/MMC drivers are working :-).

If U-Boot needs a specific DTB, shouldn't it be shipped in
u-boot/arch/riscv/dts/?


  // Marcus

  reply	other threads:[~2019-09-08 13:19 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 [this message]
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
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=yf98sqzj585.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