[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1906170419010.19994@viisi.sifive.com>
Date: Mon, 17 Jun 2019 04:34:28 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Andreas Schwab <schwab@...e.de>
cc: Yash Shah <yash.shah@...ive.com>, davem@...emloft.net,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
robh+dt@...nel.org, mark.rutland@....com,
nicolas.ferre@...rochip.com, palmer@...ive.com,
aou@...s.berkeley.edu, ynezz@...e.cz, sachin.ghadi@...ive.com
Subject: Re: [PATCH v2 0/2] Add macb support for SiFive FU540-C000
On Mon, 17 Jun 2019, Andreas Schwab wrote:
> On Jun 17 2019, Paul Walmsley <paul.walmsley@...ive.com> wrote:
>
> > On Mon, 17 Jun 2019, Andreas Schwab wrote:
> >
> >> On Jun 17 2019, Paul Walmsley <paul.walmsley@...ive.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.
- Paul
Powered by blists - more mailing lists