From: Aymeric <mulx@aplu.fr>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: netdev@vger.kernel.org, linux-amlogic@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: network unstable on odroid-c1/meson8b.
Date: Thu, 20 Jun 2019 09:55:50 +0200 [thread overview]
Message-ID: <d2e298040f4887c547da11178f9ea64f@aplu.fr> (raw)
In-Reply-To: <0df100ad-b331-43db-10a5-3257bd09938d@gmail.com>
Hi,
On 2019-06-20 00:14, Heiner Kallweit wrote:
> On 19.06.2019 22:18, Aymeric wrote:
>> Hello all,
>>
> Kernel 3.10 didn't have a dedicated RTL8211F PHY driver yet, therefore
> I assume the genphy driver was used. Do you have a line with
> "attached PHY driver" in dmesg output of the vendor kernel?
No.
Here is the full output of the dmesg from vendor kernel [¹].
I've also noticed something strange, it might be linked, but mac address
of the board is set to a random value when using mainline kernel and
I've to set it manually but not when using vendor kernel.
>
> The dedicated PHY driver takes care of the tx delay, if the genphy
> driver is used we have to rely on what uboot configured.
> But if we indeed had an issue with a misconfigured delay, I think
> the connection shouldn't be fine with just another link partner.
> Just to have it tested you could make rtl8211f_config_init() in
> drivers/net/phy/realtek.c a no-op (in current kernels).
>
I'm not an expert here, just adding a "return 0;" here[²] would be
enough?
> And you could compare at least the basic PHY registers 0x00 - 0x30
> with both kernel versions, e.g. with phytool.
>
They are not the same but I don't know what I'm looking for, so for
kernel 3.10 [³] and for kernel 5.1.12 [⁴].
Aymeric
[¹]:
https://paste.aplu.fr/?38ef95b44ebdbfc3#G666/YbhgU+O+tdC/2HaimUCigm8ZTB44qvQip/HJ5A=
[²]:
https://github.com/torvalds/linux/blob/241e39004581475b2802cd63c111fec43bb0123e/drivers/net/phy/realtek.c#L164
[³]:
https://paste.aplu.fr/?2dde1c32d5c68f4c#6xIa8MjTm6jpI6citEJAqFTLMMHDjFZRet/M00/EwjU=
[⁴]:
https://paste.aplu.fr/?32130e9bcb05dde7#N/xdnvb5GklcJtiOxMpTCm+9gsUliRwH8X3dcwSV+ng=
next prev parent reply other threads:[~2019-06-20 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 20:18 network unstable on odroid-c1/meson8b Aymeric
2019-06-19 22:14 ` Heiner Kallweit
2019-06-20 7:55 ` Aymeric [this message]
2019-06-20 15:53 ` Heiner Kallweit
2019-06-20 20:54 ` Aymeric
2019-06-23 18:16 ` Aymeric
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=d2e298040f4887c547da11178f9ea64f@aplu.fr \
--to=mulx@aplu.fr \
--cc=hkallweit1@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
/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).