Re: Problem with Orange Pi 5 ethernet PHY on NetBSD 11

[mlelstv%serpens.de@localhost (Michael van Elst)]

john%klos.com@localhost (John Klos) writes:

>[     1.000004] eqos0 at acpi0 (MAC1, RKCP6543-61): mem 0xfe1c0000-0xfe1cffff irq 266,265
>[     1.000004] eqos0: DesignWare EQOS ver 0x51 (0x30)
>[     1.000004] eqos0: hw features 1a1173f7 111e01e8 11041041 0c370031
>[     1.000004] eqos0: using 32-bit DMA
>[     1.000004] eqos0: Ethernet address 0e:f5:d1:ce:56:d0
>[     1.000004] ukphy0 at eqos0 phy 0: OUI 0xc82b5e, model 0x0011, rev. 11
>[     1.000004] ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
>[     1.000004] ukphy1 at eqos0 phy 1: OUI 0xc82b5e, model 0x0011, rev. 11
>[     1.000004] ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto


>whereas in NetBSD 11, we get mcommphy* PHYs:

>[     1.000004] mcommphy0 at eqos0 phy 0: Motorcomm YT8531 GbE PHY
>[     1.000004] mcommphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
>[     1.000004] mcommphy1 at eqos0 phy 1: Motorcomm YT8531 GbE PHY
>[     1.000004] mcommphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto



Here eqos comes with rgephy0 (RTL8211F) and that works too.

mcommphy has lots of properties to control details. But these
are not set by the ACPI attachment without FDT.

N.B. attaching the phy twice is a bug, it answers to the wildcard
address and to its own. A workaround is to set sc_phy_id in
eqos_apci.c to 0 instead of MII_PHY_ANY.