mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@badula.org>
To: "Cameron Goble" <cgoble@salud.unm.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SIS900 module detects two transceivers, picks the wrong one
Date: Mon, 3 Feb 2003 22:00:37 -0500	[thread overview]
Message-ID: <200302040300.h1430bw04813@moisil.badula.org> (raw)
In-Reply-To: <cs.lists.linux-kernel/se3e7fca.052@salud.unm.edu>

On Mon, 03 Feb 2003 14:42:08 -0700, Cameron Goble <cgoble@salud.unm.edu> wrote:

> I am having trouble with the SIS900 driver module v1.08.04. The module
> installs correctly and does not return an error, but ... well... 
> 
> Perhaps dmesg will explain better:
> 
> eth0: AMD79C901 HomePNA PHY transceiver found at address 2.
> eth0: AMD79C901 10BASE-T PHY transceiver found at address 3.
> eth0: using transceiver found at address 2 as default
> eth0: SiS 900 PCI Fast Ethernet at 0xec400, IRQ 11, 00:30:67:09:53:81.
> 
> So the network interface is a multi-function device, built onto the
> motherboard. The driver picks the HomePNA transceiver, but I want to use
> the 10BASE-T transceiver. Is there an option I can pass, or some code I
> can edit that force the driver to pick the 10BASE-T transceiver at
> address 3?

There is no such option, unfortunately. The driver attempts to find a 
transceiver with a link up, and uses that as a default. If it can't find
any, then it defauls to using the HomePNA (type HOME) transceiver.

So you have two choices:

1. make sure the interface is connected to a hub/switch when the driver
initializes;

or, if that doesn't work:

2. apply the following patch to the driver:

--- sis900.c.old	Mon Aug 26 14:43:22 2002
+++ sis900.c	Mon Feb  3 21:59:26 2003
@@ -513,6 +513,9 @@
 		u16 mii_status;
 		int i;
 
+		if (phy_addr == 2)
+			continue;
+
 		mii_phy = NULL;
 		for(i = 0; i < 2; i++)
 			mii_status = mdio_read(net_dev, phy_addr, MII_STATUS);

It's a crude hack, but it ought to work on your box.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

       reply	other threads:[~2003-02-04  2:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cs.lists.linux-kernel/se3e7fca.052@salud.unm.edu>
2003-02-04  3:00 ` Ion Badulescu [this message]
     [not found] <se3e8e6f.059@salud.unm.edu>
2003-02-03 23:22 ` Richard B. Johnson
2003-02-03 22:44 Cameron Goble
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 21:42 Cameron Goble
2003-02-03 22:12 ` Richard B. Johnson

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=200302040300.h1430bw04813@moisil.badula.org \
    --to=ionut@badula.org \
    --cc=cgoble@salud.unm.edu \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®