net: phy: marvell10g: update header comments
Update header comments to indicate the newly found behaviour with XAUI interfaces. Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> Reviewed-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
3abbcccc6f
commit
05ca1b327e
@ -6,12 +6,18 @@
|
||||
*
|
||||
* There appears to be several different data paths through the PHY which
|
||||
* are automatically managed by the PHY. The following has been determined
|
||||
* via observation and experimentation:
|
||||
* via observation and experimentation for a setup using single-lane Serdes:
|
||||
*
|
||||
* SGMII PHYXS -- BASE-T PCS -- 10G PMA -- AN -- Copper (for <= 1G)
|
||||
* 10GBASE-KR PHYXS -- BASE-T PCS -- 10G PMA -- AN -- Copper (for 10G)
|
||||
* 10GBASE-KR PHYXS -- BASE-R PCS -- Fiber
|
||||
*
|
||||
* With XAUI, observation shows:
|
||||
*
|
||||
* XAUI PHYXS -- <appropriate PCS as above>
|
||||
*
|
||||
* and no switching of the host interface mode occurs.
|
||||
*
|
||||
* If both the fiber and copper ports are connected, the first to gain
|
||||
* link takes priority and the other port is completely locked out.
|
||||
*/
|
||||
|
Loading…
x
Reference in New Issue
Block a user