| commit | 04185fc67c0f8ec84ce9dd9ef33c9825b41453c6 | |
| author | Lennert Buytenhek <buytenh@wantstofly.org> | |
| Wed, 8 Oct 2008 21:41:19 +0000 (8 23:41 +0200) | ||
| committer | Nicolas Pitre <nico@cam.org> | |
| Sun, 19 Oct 2008 18:29:05 +0000 (19 14:29 -0400) | ||
| tree | f277b7efd17bb82096859b4702a8d78447e429cb | treesnapshot (tar.gz zip) |
| parent | 0cfd81031a26717fe14380d18275f8e217571615 | commitdiff |
[ARM] mv78xx0: force link speed/duplex on eth2/eth3
On the mv78xx0 development board, eth2 and eth3 do not have
corresponding PHYs, but are internally connected, as a way of
facilitating communication between the two CPU cores. Since there are
no PHYs, we need to tell the network driver explicitly to force the
link on eth2 and eth3 up, to 1000 Mb/s full duplex.
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Signed-off-by: Nicolas Pitre <nico@marvell.com>
On the mv78xx0 development board, eth2 and eth3 do not have
corresponding PHYs, but are internally connected, as a way of
facilitating communication between the two CPU cores. Since there are
no PHYs, we need to tell the network driver explicitly to force the
link on eth2 and eth3 up, to 1000 Mb/s full duplex.
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Signed-off-by: Nicolas Pitre <nico@marvell.com>
| arch/arm/mach-mv78xx0/db78x00-bp-setup.c | diffblobblamehistory |