From: Yixun Lan <yixun.lan@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Claudiu.Beznea@microchip.com, linux-riscv@lists.infradead.org,
ckeepax@opensource.cirrus.com, andrew@lunn.ch, w@1wt.eu,
Nicolas.Ferre@microchip.com, daniel@0x0f.com,
alexandre.belloni@bootlin.com, pthombar@cadence.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: macb broken on HiFive Unleashed
Date: Fri, 19 Mar 2021 08:42:25 +0000 [thread overview]
Message-ID: <CALecT5g5NLYSemdb5i-n66vYmBTk1xNSLn24fDQgZ+uX6rmj4Q@mail.gmail.com> (raw)
In-Reply-To: <CALecT5gY1GK774TXyM+zA3J9Q8O90UKMs3bvRk13yg9_+cFO3Q@mail.gmail.com>
HI Andreas:
On Fri, Mar 19, 2021 at 8:28 AM Yixun Lan <yixun.lan@gmail.com> wrote:
>
> HI Andreas:
>
> On Wed, Mar 17, 2021 at 4:27 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
> >
> > It turned out to be a broken clock driver.
> >
>
> what's the exact root cause? and any solution?
> seems I face the same issue, upgrade kernel to 5.11, then eth0 fail to bring up
>
oh, sorry for the noise, just saw you already commented in another thread..
https://lkml.kernel.org/r/87v99qyjaz.fsf@igel.home
next prev parent reply other threads:[~2021-03-19 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 19:30 macb broken on HiFive Unleashed Andreas Schwab
2021-03-09 8:55 ` Claudiu.Beznea
2021-03-10 16:17 ` Willy Tarreau
2021-03-10 19:55 ` Andreas Schwab
2021-03-13 21:54 ` Emil Renner Berthing
2021-03-14 7:19 ` Andreas Schwab
2021-03-17 16:26 ` Andreas Schwab
2021-03-19 8:28 ` Yixun Lan
2021-03-19 8:42 ` Yixun Lan [this message]
2021-03-19 8:51 ` Andreas Schwab
2021-03-19 22:25 ` Yixun Lan
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=CALecT5g5NLYSemdb5i-n66vYmBTk1xNSLn24fDQgZ+uX6rmj4Q@mail.gmail.com \
--to=yixun.lan@gmail.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=ckeepax@opensource.cirrus.com \
--cc=daniel@0x0f.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pthombar@cadence.com \
--cc=schwab@linux-m68k.org \
--cc=w@1wt.eu \
/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).