diff options
author | James Cameron <james.cameron@hp.com> | 2006-05-10 13:33:29 -0700 |
---|---|---|
committer | Stephen Hemminger <shemminger@osdl.org> | 2006-05-10 14:04:52 -0700 |
commit | d8e95e52a9db0e26b37f51ab5140b89da7c4b31e (patch) | |
tree | 18288c758368f0147a5e47f1bae4b567d9d0b7a5 /include/asm-ppc/page.h | |
parent | 4c1b46226ce4424a93b8ac544e37afb26c8a72c6 (diff) |
sis900: phy for FoxCon motherboard
661FX7MI-S motherboard which uses the SiS 661FX chipset. The patch adds
an entry to mii_chip_info for the transceiver.
The PHY ids were found using the sis900_c_122.diff patch from
http://brownhat.org/sis900.html but that patch didn't solve the problem,
because the PHY at address 1 was already being chosen.
Without my patch, when bursts of packets arrive from other hosts on a
LAN, the interface dropped one roughly 10% of the time, causing
retransmits. There were fifth second pauses in refresh of large xterms,
and it made Netrek suck. I can provide further test data.
Workaround in lieu of patch is to use mii-tool to advertise
100baseTx-HD, then force renegotiation.
I wasn't able to identify the actual transceiver, so the description
field is a guess.
This patch is similar to Artur Skawina's patch:
http://marc.theaimsgroup.com/?l=linux-netdev&m=114297516729079&w=2
I'm not sure, but I wonder if it means the default behaviour should be
changed, so as to better handle future transceivers.
Diff is against 2.6.16.13.
Signed-off-by: James Cameron <james.cameron@hp.com>
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Diffstat (limited to 'include/asm-ppc/page.h')
0 files changed, 0 insertions, 0 deletions