From: Jeff Garzik <jgarzik@pobox.com>
To: Vergoz Michael <mvergoz@sysdoor.com>
Cc: Ducrot Bruno <poup@poupinou.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 8139too.c patch for kernel 2.4.19
Date: Mon, 18 Nov 2002 16:15:56 -0500 [thread overview]
Message-ID: <3DD9588C.8090701@pobox.com> (raw)
In-Reply-To: <028901c28ead$10dfbd20$76405b51@romain>
Vergoz Michael wrote:
> >Vergoz Michael wrote:
> >If you are seeing a problem, please describe in detail the problem so
> >that kernel developers may fix it in the current kernel's 8139too.c.
>
>
> * The problem is in packet recv, i'v to work this night to find what
> exactly
> is the problem
thanks!
>
>
> >>The driver 8139cp.c can be removed to the source entry.
> >
> >
> >This is the preferred driver for the 8139C+ chip, as it included many
> >bug fixes and is much faster than the version from RealTek.
>
>
> * I will make a prupose to all linux kernel developers about that. I
> prefere
> to fix that problem before to prupose anything else :P
Certainly. Comments from all are welcome. Here is the general argument:
8139/A/B/C/D, 8100, 8139 rev K. are all supported by 8139too.
8139C+ is a totally different chip, and thus gets a totally different
driver. The realtek 8139C+ changes (which you posted) basically add a
totally different driver into the same source code. The only reason for
this is that PCI ID for 8139C+ is similar [differs on PCI Revision Id].
finally, I emailed my RealTek contact directly, and he said RealTek has
found no problems with 8139cp.c driver, and they support 8139cp's use.
Regards,
Jeff
next prev parent reply other threads:[~2002-11-18 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 2:49 8139too.c patch for kernel 2.4.19 Vergoz Michael
2002-11-18 7:34 ` Jeff Garzik
2002-11-18 8:50 ` Vergoz Michael
2002-11-18 17:04 ` Ducrot Bruno
2002-11-18 9:05 ` Jeff Garzik
2002-11-18 11:17 ` Andreas Steinmetz
2002-11-18 15:55 ` Jeff Garzik
2002-11-18 16:12 ` Andreas Steinmetz
2002-11-18 16:47 ` Jeff Garzik
2002-11-18 17:25 ` Jeff Garzik
2002-11-18 17:51 ` Vergoz Michael
2002-11-18 18:14 ` Jeff Garzik
2002-11-18 20:04 ` Vergoz Michael
2002-11-18 21:15 ` Jeff Garzik [this message]
2002-11-18 21:34 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 17:15 Manfred Spraul
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=3DD9588C.8090701@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mvergoz@sysdoor.com \
--cc=poup@poupinou.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