netdev - Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <GyVvHJnPCxv3x_uGwaDIu_KKQgeFhh24x4aRcVQ0WQVr4tjxubB3qeWiSGVmwy8VbKrAQ2nF0iUDLHPTgE7M9ZiOqW1XQ5nTYgzyIcl-VZc=@proton.me>
Date: Wed, 24 Sep 2025 01:33:00 +0000
From: Zoo Moo <zoomoo100@...ton.me>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Marcin Wojtas <mw@...ihalf.com>
Subject: Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?






Sent with Proton Mail secure email.

On Monday, 22 September 2025 at 19:22, Russell King (Oracle) <linux@...linux.org.uk> wrote:

> On Mon, Sep 22, 2025 at 08:58:49AM +0000, Zoo Moo wrote:
> 

> > Sent with Proton Mail secure email.
> > 

> > On Sunday, 21 September 2025 at 19:56, Russell King (Oracle) linux@...linux.org.uk wrote:
> > 

> > > On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> > 

> > > > Hi,
> > 

> > > > Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.
> > 

> > > Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
> > > isn't correct. Just a guess based on the problems that RGMII normally
> > > causes.
> > 

> > Hi Russell,
> > 

> > Thanks, we did try different drivers (gmii, sgmii), but they didn't help, details in this message https://forum.doozan.com/read.php?2,138851,139291#msg-139291.
> 

> 

> What I was meaning was not to try stuff like "SGMII", but try the other
> three flavours of RGMII. In other words:
> 

> rgmii
> rgmii-txid
> rgmii-rxid
> 

> If u-boot works, and it's using RGMII, then it's definitely one of the
> four flavours of RGMII interface.
> 

> No need to post the failures of the testing to the forums - just say
> here whether any of those result in packet flow or not. Nothing else
> should change - the only difference between these modes are the timings
> of the RGMII interface, and having the wrong mode is the most common
> reason for RGMII not working.
> 

> Thanks.
> 

> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

Thanks Russel,

I tried all flavours again (rgmii, rgmii-id, rgmii-txid and rgmii-rxid), but all resulted in the same outcome. 


ifconfig shows it sends packets, but nothing is received. I cannot detect it actually sending any packets from the device though.

For example:

root@(none):~# ifconfig eth0 192.168.27.111 netmask 255.255.255.0 up hw ether 00:11:22:33:44:55
[   31.727773][ T2055] mvpp2 f10f0000.ethernet eth0: PHY [f10c0054.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[   31.738178][ T2055] mvpp2 f10f0000.ethernet eth0: configuring for phy/rgmii-txid link mode
[   36.007360][   T10] mvpp2 f10f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off

root@(none):~# dhclient eth0
root@(none):~# ifconfig eth0                                                   

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                     

        inet 192.168.27.111  netmask 255.255.255.0  broadcast 192.168.27.255
        inet6 <IP6 ADDRESS>  prefixlen 64  scopeid 0x20<link>
        ether 00:11:22:33:44:55  txqueuelen 2048  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 71  bytes 4858 (4.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Do I need to adjust the internal delays? rx-internal-delay-ps/tx-internal-delay-ps

(reference: https://www.thegoodpenguin.co.uk/blog/linux-ethernet-phy-mode-bindings-explained/)

Is it something we can determine by looking at the Synology kernel source?
Download attachment "publickey - zoomoo100@...ton.me - 0x1C985C6F.asc" of type "application/pgp-keys" (836 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (344 bytes)