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 13:14:00 -0500 [thread overview]
Message-ID: <3DD92DE8.7030501@pobox.com> (raw)
In-Reply-To: <028901c28ead$10dfbd20$76405b51@romain>
Vergoz Michael wrote:
> Hi list,
>
> The driver that i have post support realtek 8139A/B/C/D/C+ (already
> tested)
> and another dlink card (realtek based).
> On certain motherboard where the chip is integred you will perhaps
> have some
> troubles.
Would you be willing to work with Linux kernel developers to integrate
the useful changes in this driver into the kernel?
The driver you posted is my driver, version 0.9.15, which is an older
version of the kernel's driver and doesn't include many changes made
since then.
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 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.
Jeff
next prev parent reply other threads:[~2002-11-18 18:07 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 [this message]
2002-11-18 20:04 ` Vergoz Michael
2002-11-18 21:15 ` Jeff Garzik
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=3DD92DE8.7030501@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