From: Troy Benjegerdes <troy.benjegerdes@sifive.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Andreas Schwab <schwab@suse.de>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>,
netdev@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
nicolas.ferre@microchip.com,
Sachin Ghadi <sachin.ghadi@sifive.com>,
Yash Shah <yash.shah@sifive.com>,
robh+dt@kernel.org, ynezz@true.cz,
linux-riscv@lists.infradead.org, davem@davemloft.net,
Jim Jacobsen <jamez@wit.com>
Subject: Re: [PATCH v2 0/2] Add macb support for SiFive FU540-C000
Date: Mon, 17 Jun 2019 09:14:25 -0500 [thread overview]
Message-ID: <F48A4F7F-0B0D-4191-91AD-DC51686D1E78@sifive.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906170419010.19994@viisi.sifive.com>
> On Jun 17, 2019, at 6:34 AM, Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> On Mon, 17 Jun 2019, Andreas Schwab wrote:
>
>> On Jun 17 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
>>
>>> On Mon, 17 Jun 2019, Andreas Schwab wrote:
>>>
>>>> On Jun 17 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
>>>>
>>>>> Looks to me that it shouldn't have an impact unless the DT string is
>>>>> present, and even then, the impact might simply be that the MACB driver
>>>>> may not work?
>>>>
>>>> If the macb driver doesn't work you have an unusable system, of course.
>>>
>>> Why?
>>
>> Because a system is useless without network.
>
> From an upstream Linux point of view, Yash's patches should be an
> improvement over the current mainline kernel situation, since there's
> currently no upstream support for the (SiFive-specific) TX clock switch
> register. With the right DT data, and a bootloader that handles the PHY
> reset, I think networking should work after his patches are upstream --
> although I myself haven't tried this yet.
>
Have we documented this tx clock switch register in something with a
direct URL link (rather than a PDF)?
I’d like to update freedom-u-sdk (or yocto) to create bootable images
with a working U-boot (upstream or not, I don’t care, as long as it works),
and what I have right now is the old legacy HiFive U-boot[1] and a 4.19
kernel with a bunch of extra patches.
The legacy M-mode U-boot handles the phy reset already, and I’ve been
able to load upstream S-mode uboot as a payload via TFTP, and then
load and boot a 4.19 kernel.
It would be nice to get this all working with 5.x, however there are still
several missing pieces to really have it work well.
[1] https://github.com/sifive/HiFive_U-Boot
next prev parent reply other threads:[~2019-06-17 14:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 4:19 Yash Shah
2019-06-17 4:19 ` [PATCH v2 1/2] macb: bindings doc: add sifive fu540-c000 binding Yash Shah
2019-06-17 8:56 ` Paul Walmsley
2019-06-17 4:19 ` [PATCH v2 2/2] macb: Add support for SiFive FU540-C000 Yash Shah
2019-06-17 15:58 ` Andrew Lunn
2019-06-18 4:04 ` Yash Shah
2019-06-17 4:43 ` [PATCH v2 0/2] Add macb " Yash Shah
2019-06-17 8:25 ` Andreas Schwab
2019-06-17 9:58 ` Paul Walmsley
2019-06-17 10:01 ` Andreas Schwab
2019-06-17 10:05 ` Paul Walmsley
2019-06-17 10:14 ` Andreas Schwab
2019-06-17 11:34 ` Paul Walmsley
2019-06-17 14:14 ` Troy Benjegerdes [this message]
2019-06-17 14:20 ` Paul Walmsley
2019-06-17 18:42 ` Alistair Francis
2019-06-18 3:26 ` Paul Walmsley
2019-06-18 9:32 ` Anup Patel
2019-06-18 16:49 ` Troy Benjegerdes
2019-06-18 23:40 ` Atish Patra
2019-06-18 23:11 ` Alistair Francis
2019-06-17 10:22 ` Yash Shah
2019-06-17 10:28 ` Paul Walmsley
2019-06-17 11:15 ` Yash Shah
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=F48A4F7F-0B0D-4191-91AD-DC51686D1E78@sifive.com \
--to=troy.benjegerdes@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jamez@wit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=schwab@suse.de \
--cc=yash.shah@sifive.com \
--cc=ynezz@true.cz \
/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
all inboxes | Powered by JetHome®