diff options
author | Peter Tyser <ptyser@xes-inc.com> | 2009-11-03 17:52:07 -0600 |
---|---|---|
committer | Ben Warren <biggerbadderben@gmail.com> | 2010-01-31 22:34:34 -0800 |
commit | 46e91674fb4b6d06c6a4984c0b5ac7d9a16923f4 (patch) | |
tree | 1cf4646126982bfc501bffa3067d1c1241499226 /api | |
parent | 76771e595aa2640da8c7b5ea81bd9583ccdab8a1 (diff) | |
download | u-boot-imx-46e91674fb4b6d06c6a4984c0b5ac7d9a16923f4.zip u-boot-imx-46e91674fb4b6d06c6a4984c0b5ac7d9a16923f4.tar.gz u-boot-imx-46e91674fb4b6d06c6a4984c0b5ac7d9a16923f4.tar.bz2 |
tsec: Force TBI PHY to 1000Mbps full duplex in SGMII mode
In SGMII mode the link between a processor's internal TBI PHY and an
external PHY should always be 1000Mbps, full duplex. Also, the SGMII
interface between an internal TBI PHY and external PHY does not
support in-band auto-negotation.
Previously, when configured for SGMII mode a TBI PHY would attempt to
restart auto-negotation during initializtion. This auto-negotation
between a TBI PHY and external PHY would fail and result in unusable
ethernet operation.
Forcing the TBI PHY and and external PHY to link at 1000Mbps full duplex
in SGMII mode resolves this issue of auto-negotation failing.
Note that 10Mbps and 100Mbps operation is still possible on the external
side of the external PHY even when SGMII is operating at 1000Mbps.
The SGMII interface still operates at 1000Mbps, but each byte of data
is repeated 100 or 10 times for 10/100Mbps and the external PHY handles
converting this data stream into proper 10/100Mbps signalling.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Signed-off-by: Ben Warren <biggerbadderben@gmail.com>
Diffstat (limited to 'api')
0 files changed, 0 insertions, 0 deletions