From: Aymeric <mulx@aplu.fr>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org
Subject: Re: Meson8b network not stable at gigabit
Date: Wed, 19 Jun 2019 10:20:42 +0200 [thread overview]
Message-ID: <b0e028410f5b0b21584fd654f8446edf@aplu.fr> (raw)
In-Reply-To: <CAFBinCDLaz4GebHgVo6P6C9ZtL5LtihVczAyuaRN+mnXKhHuzw@mail.gmail.com>
Hi Martin,
On 2019-06-17 21:36, Martin Blumenstingl wrote:
> Hi Aymeric,
>
> too bad, that was the only "smart" idea I had.
No problem, that was more than me. :)
>
> did see this issue with kernel versions earlier than 5.0 as well?
> then you can try to git bisect the cause
I've made a switch from 3.10 to 5.0.4 directly (and the issue was
already there, I just didn't had time to report/investigate), so I don't
know is the issue was present in any earlier version.
>
> you can also send a similar mail to the netdev mailing list (please
> keep the Amogic list at least Cc'ed) and ask for help there
> the Amlogic SoCs use a DesignWare MAC (Ethernet controller, the driver
> is called stmmac) with a Relatek RTL8211F Ethernet PHY.
> there's little Amlogic specific registers involved: they mostly
> control the PHY interface (enabling RMII or RGMII) and the clocks
> so it's very likely that someone on the netdev list has an idea how to
> debug this because a large part of the Ethernet setup is not Amlogic
> SoC specific
>
Okay, I'll do it by the end of the week!
BR,
Aymeric.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-06-19 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 22:22 Meson8b network not stable at gigabit Aymeric
2019-06-15 11:34 ` Martin Blumenstingl
2019-06-16 16:05 ` Aymeric
2019-06-16 16:30 ` Martin Blumenstingl
2019-06-16 18:57 ` Aymeric
2019-06-17 19:36 ` Martin Blumenstingl
2019-06-19 8:20 ` Aymeric [this message]
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=b0e028410f5b0b21584fd654f8446edf@aplu.fr \
--to=mulx@aplu.fr \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.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).