netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Cameron <james.cameron@hp.com>
To: venza@brownhat.org, netdev@vger.kernel.org
Subject: [PATCH] sis900 Foxconn 661FX7MI-S PHY support
Date: Wed, 10 May 2006 10:04:50 +1000	[thread overview]
Message-ID: <20060510000450.GA5448@hp.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

This patch is required to get sis900 ethernet working well on a Foxconn
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>

[-- Attachment #2: sis900_661fx.diff --]
[-- Type: text/plain, Size: 509 bytes --]

--- sis900.c.orig	2006-05-09 10:36:54.000000000 +1000
+++ sis900.c	2006-05-09 12:16:26.000000000 +1000
@@ -127,6 +127,7 @@
 } mii_chip_table[] = {
 	{ "SiS 900 Internal MII PHY", 		0x001d, 0x8000, LAN },
 	{ "SiS 7014 Physical Layer Solution", 	0x0016, 0xf830, LAN },
+	{ "SiS 900 on Foxconn 661 7MI",         0x0143, 0xBC70, LAN },
 	{ "Altimata AC101LF PHY",               0x0022, 0x5520, LAN },
 	{ "AMD 79C901 10BASE-T PHY",  		0x0000, 0x6B70, LAN },
 	{ "AMD 79C901 HomePNA PHY",		0x0000, 0x6B90, HOME},

             reply	other threads:[~2006-05-10  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  0:04 James Cameron [this message]
     [not found] ` <20060510103109.148197cd@localhost.localdomain>
2006-05-10 20:17   ` [PATCH] sis900 Foxconn 661FX7MI-S PHY support Daniele Venzano
  -- strict thread matches above, loose matches on Subject: below --
2006-05-11  0:05 James Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060510000450.GA5448@hp.com \
    --to=james.cameron@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=venza@brownhat.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).