From: Jason Lunz <lunz@falooley.org>
To: netdev@oss.sgi.com
Cc: Robert.Olsson@data.slu.se, greearb@candelatech.com,
garzik@mandrakesoft.com
Subject: [ANNOUNCE] NAPI patches for 2.4.19-rc1
Date: Wed, 10 Jul 2002 18:32:37 -0400 [thread overview]
Message-ID: <20020710223237.GA7995@orr.falooley.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
I've backported the most recent napi sources I could find to 2.4.19-rc1.
The patches are available at http://orr.falooley.org/pub/linux/net/.
Testing and suggestions are welcome. Currently backported napi drivers
are e1000, eepro100, tulip, and 3c59x. I intend to backport dl2k and
sundance at some point, but I have no dl2k cards and I'm working with
Donald Becker to get the sundance driver working on the card I have.
Does anyone know of more recent NAPI conversions? Robert Olsson tells me
Jeff Garzik has a more recent tulip conversion, but there are _no_ napi
net drivers in 2.5.25 and I haven't found any others except for those
mentioned at the NAPI ftp site.
Jason
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-07-10 22:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 22:32 Jason Lunz [this message]
2002-07-10 22:56 ` [ANNOUNCE] NAPI patches for 2.4.19-rc1 Ben Greear
2002-07-11 13:20 ` Jason Lunz
2002-07-10 23:34 ` jamal
2002-07-11 0:41 ` Donald Becker
2002-07-11 14:57 ` Jeff Garzik
2002-07-11 16:50 ` Donald Becker
2002-07-11 17:17 ` Ben Greear
2002-07-11 18:31 ` Jeff Garzik
2002-07-11 22:31 ` Ben Greear
2002-07-12 15:11 ` Jason Lunz
2002-07-11 18:53 ` Donald Becker
2002-07-11 19:34 ` Jeff Garzik
2002-07-11 13:26 ` Jason Lunz
2002-07-11 13:39 ` Jeff Garzik
2002-07-11 13:44 ` Jason Lunz
2002-07-11 14:33 ` Donald Becker
2002-07-11 14:37 ` Jeff Garzik
2002-07-11 16:00 ` Robert Olsson
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=20020710223237.GA7995@orr.falooley.org \
--to=lunz@falooley.org \
--cc=Robert.Olsson@data.slu.se \
--cc=garzik@mandrakesoft.com \
--cc=greearb@candelatech.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).