netdev - Re: DSA with MV88E6321 and imx28

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

Date:   Thu, 6 Jun 2019 15:27:22 +0200
From:   Benjamin Beckmeyer <beb@...-engel.de>
To:     Andrew Lunn <andrew@...n.ch>, <netdev@...r.kernel.org>
Subject: Re: DSA with MV88E6321 and imx28


On 06.06.19 14:24, Andrew Lunn wrote:
> On Thu, Jun 06, 2019 at 10:49:08AM +0200, Benjamin Beckmeyer wrote:
>>>> I removed all phy-handle for the internal ports and in the mdio part 
>>>> is only port 2 and 6 by now. But the Serdes ports are still not be
>>>> recognized. So maybe there is still something wrong?
>>> What do you mean by SERDES? Do you mean they are connected to an SFP
>>> cage? If so, you need to add an SFP node. Take a look at
>>> vf610-zii-dev-rev-c.dts for an example.
>>>
>>> 	Andrew
>> Hey Andrew,
>> I've looked into the device tree. Why do they reference to i2c? We have
>> 1x8 SFF tranceivers. Should I just add an i2c entry for it, because the 
>> value is required?
> Hi Benjamin
>
> Do you have a diagram of the board you can share with me. I'm confused
> about which ports have external copper PHYs and which have SFF
> connected to them., and if you are using copper PHYs with SERDES
> interfaces not RGMII.
>
> Each port needs to have some sort of 'PHY' connected to it. Either a
> copper PHY, an SFP/SFF, or a fake PHY using fixed-link.
>
>> Do you know which switch chip they use in the  vf610-zii-dev-rev-c?
> That board uses two 6390X. There is also ZII CF1 is if i remember
> correctly a 6352, and has one SFF.
>
> If you have an SFF connected to a port, you need its i2c bus, so that
> PHYLINK can read the SFF EEPROM to determine its capabilities and
> correctly configure the MAC to fit the SFF. Plus you get all the
> diagnostics, etc.
>
>   Andrew

Hi Andrew,
>From our hardware developer I know now that we are using a "mini" SFF 
which has no i2c eeprom. 

Switch				|	external
Port 0 - internal serdes 0x0c --|-------Mini SFF 1x8 Transceiver
				|
Port 0 - internal serdes 0x0d --|-------Mini SFF 1x8 Transceiver
				|
Port 2 ----------RGMII----------|-------KSZ9031 PHY 0x02(strap)--Transceiver
				|
Port 3 - internal PHY 0x03 -----|-------Transceiver
				|
Port 3 - internal PHY 0x04 -----|-------Transceiver
				|			
Port 5 - CPU-Port RMII ---------|-------CPU
				|
Port 6 ----------RGMII----------|-------KSZ9031 PHY 0x06(strap)--Transceiver


Hopefully this makes it more clear to you.