From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: 8139 full duplex?
Date: Fri, 16 Feb 2001 11:03:13 +0100 (MET) [thread overview]
Message-ID: <200102161003.LAA02713@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.3.96.1010216034551.6404E-100000@mandrakesoft.mandrakesoft.com> from Jeff Garzik at "Feb 16, 2001 03:46:44 am"
Jeff Garzik wrote:
> On Fri, 16 Feb 2001, Rogier Wolff wrote:
> > I have a bunch of computers with 8139 cards. When I moved the cables
> > over from my hub to my new switch all the "full duplex" lights came on
> > immediately.
> >
> > Would this mean that the driver/card already were in full-duplex? That
> > would explain me seeing way too many collisions on that old hub (which
> > obviously doesn't support full-duplex).
> >
> > (Some machines run 2.2 kernels, others run 2.4 kernels some run the
> > old driver, others run the 8139too driver).
>
> Some versions of the driver bork the LED register, which may lead to
> false assumptions.
Does the driver control the led on my switch?????
(My cards just have a "link" led, and a "100Mbps" led)
I'm not going back to the hub after upgrading just to see the
changeover messages. I'm confident that we're running full-duplex now
on the switch and that that's OK with the switch. I was just wondering
wether this confirmed my suspicion that there was something wrong with
the /duplexicity/.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-02-16 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 8:58 8139 full duplex? Rogier Wolff
2001-02-16 9:32 ` James Sutherland
2001-02-16 9:40 ` Rogier Wolff
2001-02-16 10:52 ` Roeland Th. Jansen
2001-02-16 11:15 ` James Sutherland
2001-02-16 9:46 ` Jeff Garzik
2001-02-16 10:03 ` Rogier Wolff [this message]
2001-02-16 11:19 ` James Sutherland
2001-02-16 10:09 ` Alan Cox
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=200102161003.LAA02713@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--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