From: Roger Luethi <rl@hellgate.ch>
To: Donald Becker <becker@scyld.com>
Cc: netdev@oss.sgi.com
Subject: Re: pci-skeleton duplex check
Date: Thu, 12 Dec 2002 14:20:33 +0100 [thread overview]
Message-ID: <20021212132033.GA3224@k3.hellgate.ch> (raw)
In-Reply-To: <Pine.LNX.4.44.0212112108070.10674-100000@beohost.scyld.com>
On Wed, 11 Dec 2002 21:42:44 -0500, Donald Becker wrote:
> Note that the second check ignores 100baseT4, despite it have priority
> over 10baseT-*. That was intentional to work around, "a specific issue"
> with a transceiver.
That "specific issue" might be worth documenting. Information on such
quirks is hardest to come by.
> The is no extra cost to the extra bit, and it makes it clear we are
> testing for 10baseT-FDX.
> (The test was originally implemented as part of a complete set of
> cases. The test code needed while building a driver is more complex
> than what you see in the concise final result.)
That was exactly the kind of answer I've been looking for. Nothing beats
some historic background. Thank you.
Roger
next prev parent reply other threads:[~2002-12-12 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 13:24 pci-skeleton duplex check Roger Luethi
2002-12-12 2:42 ` Donald Becker
2002-12-12 13:20 ` Roger Luethi [this message]
2002-12-12 14:11 ` Donald Becker
2002-12-12 20:32 ` Jeff Garzik
2002-12-12 21:11 ` Donald Becker
2002-12-12 21:39 ` Jeff Garzik
2002-12-13 1:18 ` Donald Becker
2002-12-13 9:17 ` David S. Miller
2002-12-13 16:56 ` Donald Becker
2002-12-13 18:29 ` David S. Miller
2002-12-13 20:57 ` Jeff Garzik
2002-12-12 23:08 ` Ben Greear
2002-12-14 0:19 ` Michael Richardson
2002-12-14 1:43 ` Oliver Xymoron
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=20021212132033.GA3224@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=becker@scyld.com \
--cc=netdev@oss.sgi.com \
/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).