From: Donald Becker <becker@scyld.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
pat@isis.co.za, linux-kernel@vger.kernel.org, Alan@redhat.com
Subject: Re: PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On)
Date: Fri, 2 Mar 2001 17:48:15 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.10.10103021743390.879-100000@vaio.greennet> (raw)
In-Reply-To: <3AA01CAF.98726DEC@colorfullife.com>
On Fri, 2 Mar 2001, Manfred Spraul wrote:
> Jeff Garzik wrote:
> > Manfred Spraul wrote:
> > > Could you double check the code in tulip_core.c, around line 1450?
> > > IMHO it's bogus.
> > >
> > > 1) if the network card contains multiple mii's, then the the advertised
> > > value of all mii's is changed to the advertised value of the first mii.
...
> > If you have a single controller with multiple MII phys... how does one
> > select the phy of choice (for tulip, in the absence of SROM media
> > table...)?
>
> I'd choose the first one with a link partner.
Well, yes, but what is "first"?
Are there any Tulip cards (besides the Comet-2 w/HPNA) that have multiple
MII transceivers?
The Comet2 is a special case, since only one transceiver is powered and
visible at a time. Polling the other transceiver switches off the
first.
> > And once phy A has been selected out of N available as the
> > active phy, should you care about the others at all?
>
> Not until the link beat disappears.
Uhmm, but you don't always know when you have lost link beat. In some
cases the driver does basic polling to check for duplex changes, but
the semantics are not as clean as you would expect.
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
next prev parent reply other threads:[~2001-03-02 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 10:32 PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-02-26 20:10 ` Jeff Garzik
2001-02-26 20:58 ` Manfred Spraul
2001-03-02 21:15 ` Jeff Garzik
2001-03-02 21:03 ` I/O problem with sustained writes Collectively Unconscious
2001-03-02 23:57 ` Andrew Morton
2001-03-02 22:20 ` PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-03-02 22:48 ` Donald Becker [this message]
2001-02-27 6:16 ` Pat Verner
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 6:31 Pat Verner
2001-02-26 7:45 Pat Verner
2001-02-22 7:56 PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) NIC Pat Verner
2001-02-22 10:42 ` PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Alan Cox
2001-02-22 20:12 ` Jeff Garzik
2001-02-22 12:42 ` Pat Verner
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=Pine.LNX.4.10.10103021743390.879-100000@vaio.greennet \
--to=becker@scyld.com \
--cc=Alan@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=pat@isis.co.za \
/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).