From: Ducrot Bruno <poup@poupinou.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
list linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: RTL8139D support for 2.4?
Date: Mon, 18 Nov 2002 20:32:48 +0100 [thread overview]
Message-ID: <20021118193248.GE27595@poup.poupinou.org> (raw)
In-Reply-To: <3DD931BA.9040407@pobox.com>
On Mon, Nov 18, 2002 at 01:30:18PM -0500, Jeff Garzik wrote:
> Eyal Lebedinsky wrote:
>
> >I recently got a local (Australian, NetComm) NIC that uses a 8139D.
> >The standard 8139too seems to work with it but I wonder if I can
^^^^^^^^^^^^^^^^
> >get something more out of a driver that has extra support.
>
> [...]
>
> >Anyone knows the difference between the 8139C and 8139D?
>
>
>
> At the driver level, there should not be appreciable differences between
> the two chips. 8139C+ is the super-cool tulip-like chip from RealTek
> with all the speed and features. 8139D is just a small incremental
> revision of the chip. It does add a few features, but none that would
> affect performance or stability (positively or negatively).
>
> RealTek's 8139C+, and it's GigE cousin 8169 are really nice. I hope
> RealTek finds a lot of customers for these chips, because so far they
> are both solid, fast, and feature-full.
>
Do we have to assume that Eyal Lebedinsky should use 8139cp driver
instead of 8139too ?
Cheers,
--
Ducrot Bruno
http://www.poupinou.org Page profaissionelle
http://toto.tu-me-saoules.com Haume page
next prev parent reply other threads:[~2002-11-18 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 9:38 Eyal Lebedinsky
2002-11-18 18:30 ` Jeff Garzik
2002-11-18 19:32 ` Ducrot Bruno [this message]
2002-11-18 19:48 ` Jeff Garzik
2002-11-18 21:13 ` Mike Dresser
2002-11-18 21:21 ` Jeff Garzik
2002-11-18 22:02 ` Mike Dresser
2002-11-18 22:13 ` Jeff Garzik
2002-11-18 22:16 ` Mike Dresser
2002-11-18 22:24 ` Jeff Garzik
2002-11-18 22:33 ` Mike Dresser
2002-11-18 22:41 ` Jeff Garzik
2002-11-18 22:50 ` Mike Dresser
2002-11-18 22:57 ` Mike Dresser
2002-11-19 0:34 ` Val Henson
2002-11-19 12:15 ` Dave Jones
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=20021118193248.GE27595@poup.poupinou.org \
--to=poup@poupinou.org \
--cc=eyal@eyal.emu.id.au \
--cc=jgarzik@pobox.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
all inboxes | Powered by JetHome®