From: Troy Benjegerdes <troy.benjegerdes@sifive.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Yash Shah <yash.shah@sifive.com>
Cc: "Anup Patel" <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: Sat, 25 May 2019 13:40:07 -0500 [thread overview]
Message-ID: <AC197BDD-8A15-421E-9F99-ADFE50360982@sifive.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1905251058100.15661@viisi.sifive.com>
> On May 25, 2019, at 1:09 PM, Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> On Fri, 24 May 2019, Troy Benjegerdes wrote:
>
>> I have no issues updating the PRCI driver DT format if we also have the
>> rest of the DT entries needed to boot a working system
>
> Now is the time to fix the U-boot PRCI issue upstream. Fixing that should
> be straightforward, and should be enough to boot the system with initramfs
> and a serial console. The missing patch is currently blocking others from
> using U-boot-based boot flows on Aloe.
I suppose we have different opinions on what’s blocking what.
If https://github.com/sifive/HiFive_U-Boot is not sufficient for U-boot based
development flows, I’d like to hear what it would need to be useful until I
have a full patch set for upstream U-boot that includes mainline-bound DTS
entries that can replicate the functionality the existing legacy u-boot port
has.
>> I just have not seen an example of that other than what I have at
>> https://github.com/sifive/HiFive_U-Boot/blob/regression/arch/riscv/dts/hifive_u540.dts
>
> I sent you a pointer to a branch a few days ago that contains the most
> recent mainline-bound DTS data. That should be enough to verify that the
> basic boot works. If you want to keep up with the ongoing development of
> that data, the best bet is to subscribe to the linux-riscv mailing list.
>
>
> - Paul
I consider ‘basic boot’ to include a bootloader that can load BBL/SBI and
an payload (S-mode uboot, or a kernel/ramdisk/dtb/etc) via the network.
So this would be the time to agree on what the gemgxl/ethernet entries
should look like, and all of this can get unblocked. What I have now that
I know works (with the legacy u-boot) is this:
L51: cadence-gemgxl-mgmt@100a0000 {
compatible = "sifive,cadencegemgxlmgmt0";
reg = <0x0 0x100a0000 0x0 0x1000>;
reg-names = "control";
#clock-cells = <0>;
};
L52: ethernet@10090000 {
compatible = "cdns,macb";
interrupt-parent = <&L4>;
interrupts = <53>;
reg = <0x0 0x10090000 0x0 0x2000>;
reg-names = "control";
local-mac-address = [00 00 00 00 00 00];
phy-mode = "gmii";
clock-names = "pclk", "hclk", "tx_clk";
clocks = <&prci 1>, <&prci 1>, <&L51>;
#address-cells = <1>;
#size-cells = <0>;
phy1: ethernet-phy@0 {
reg = <0>;
reset-gpios = <&L31 12 1>;
};
};
_______________________________________________
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-25 18:40 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
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 [this message]
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=AC197BDD-8A15-421E-9F99-ADFE50360982@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 \
--cc=yash.shah@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).