netdev - Re: PHYless ethernet switch MAC-MAC serdes connection

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <loom.20150121T075010-767@post.gmane.org>
Date:	Wed, 21 Jan 2015 07:09:45 +0000 (UTC)
From:	Vijay <katoch.vijay@...il.com>
To:	netdev@...r.kernel.org
Subject: Re: PHYless ethernet switch MAC-MAC serdes connection

Florian Fainelli <f.fainelli <at> gmail.com> writes:

> 
> Do lan1 and lan2 interfaces set the RUNNING flag, which would indicate
> that the switch driver has detected a carrier for these individual 
ports?
> 
> Is the DSA switch driver correctly polling for LAN ports link 
statuses?
> 

Yes RUNNING flag is set.
Whenever I unplug/plug Ethernet cable. I see notification from dsa about 
link up/down correctly.

> 
> DSA registers a slave MDIO bus interface which calls into the "real"
> MDIO bus hardware to talk to the switch. In your case, you have both 
an
> external switch and an external PHY connected to the same MDIO bus,
> which is fine.
> 
> Your DT looks sane, although I suspect that lan2's PHY address is 3, 
and
> not 2, as address 0 is typically a special MDIO broadcast address, so
> Port 0's PHY can be read at PHY addr 1, Port 1's PHY can be read at 
PHY
> addr 2 etc... If you remove "lan2", does it work slightly better?
> 

No, lan 1 and lan2 addresses are 0 and 1 respectively. I have logged 
these values and these are printed on console as:

DSA: dsa.c: Init slave bus
DSA: slave.c: dsa_slave_mii_bus_init sw addr =0x1f , slave_mii_bus_id = 
0x0
DSA: dsa.c: register created slave_mii_bus
Debug: drivers/net/phy/phy_device.c: Creating PHY-> phy_id = 0x1410c89, 
addr = 0x0
Creating PHY-> AUTONEG_ENABLE for phy_id = 0x1410c89, addr = 0x0
Debug: drivers/net/phy/phy_device.c: Creating PHY-> phy_id = 0x1410c89, 
addr = 0x1
Creating PHY-> AUTONEG_ENABLE for phy_id = 0x1410c89, addr = 0x1
libphy: dsa slave smi: probed
net lan1: PHY already attached
DSA: slave.c: mii_bus-> name = dsa slave smi , id =dsa-0:1f
net lan2: PHY already attached
DSA: slave.c: mii_bus-> name = dsa slave smi , id =dsa-0:1f

My eth0 fixed-link address is also 0 and eth1 PHY address is 1.

Removing lan2 is not improving the situation.
Even if I do not set up eth1. Then same issue is happening between lan1 
and lan2. Whichever is configured first ( using ifconfig) is able to 
transmit packet (Tx increments). And rest all ports ( lan2) are just 
receiving (their Tx counters remain 0). Even if I ping to lan2 ip, 
response will be received only when ethernet cable is plugged to lan1 ( 
because it will only be able transmit the response), It does not matter 
if cable is plugged to lan2 port.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html