From: David Dillow <dillowd@y12.doe.gov>
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: 3Com 3cr990 driver release
Date: Fri, 14 Feb 2003 02:50:02 -0500 [thread overview]
Message-ID: <3E4C9FAA.FC8A2DC7@y12.doe.gov> (raw)
Finally, after too many delays, I am pleased to announce the release of my
driver for 3Com's 3cr990 family of network cards.
This initial release is endian clean, tested on x86 and sparc64, and does
- NAPI
- Zerocopy Tx
- TCP segmentation
- Hardware VLAN accel
It does *not* do IPSEC crypto offload as of yet. I have a version for the 2.4
series of kernels, but it is an ugly, ugly kludge, and would be shot if seen
in public. I will be working on integrating the hardware with the IPSEC
support in 2.5.x.
There are a few issues with the firmware -- DMA to a 2 byte aligned address
hangs the firmware, so we cannot easily align the IP header, and the firmware
will always strip the VLAN tags on packet reception, regardless of our
desires. I hope to work with 3Com to resolve these issues.
The code is available via BK at
http://typhoon.bkbits.net/typhoon-2.4
http://typhoon.bkbits.net/typhoon-2.5
Diffstats:
typhoon-2.4:
Documentation/Configure.help | 18
MAINTAINERS | 6
drivers/net/Config.in | 3
drivers/net/Makefile | 1
drivers/net/typhoon-firmware.h | 4108 ++++++++++++++++++++++++++++++++++++
drivers/net/typhoon.c | 2505 ++++++++++++++++++++
drivers/net/typhoon.h | 613 ++++++
include/linux/pci_ids.h | 8
8 files changed, 7262 insertions(+)
typhoon-2.5:
MAINTAINERS | 6
drivers/net/Kconfig | 20
drivers/net/Makefile | 1
drivers/net/Makefile.lib | 1
drivers/net/typhoon-firmware.h | 4108 ++++++++++++++++++++++++++++++++++++
drivers/net/typhoon.c | 2505 ++++++++++++++++++++
drivers/net/typhoon.h | 613 ++++++
include/linux/pci_ids.h | 8
8 files changed, 7262 insertions(+)
I'd like to thank 3Com's engineers for finding me documentation and putting up
with my questions, and my project manager for navigating the bureaucracy so
that this work may see public use. I couldn't have received a better going
away present on my last day on the job.
Enjoy!
David Dillow
dillowd@y12.doe.gov (old)
dave@thedillows.org (new)
next reply other threads:[~2003-02-14 7:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 7:50 David Dillow [this message]
2003-02-14 8:20 ` 3Com 3cr990 driver release Jeff Garzik
2003-02-14 14:33 ` Alan Cox
2003-02-14 15:19 ` Larry McVoy
2003-02-14 16:54 ` Alan Cox
2003-02-14 16:09 ` Larry McVoy
2003-02-14 17:23 ` Alan Cox
2003-02-14 16:36 ` Larry McVoy
2003-02-14 17:04 ` Tomas Szepe
2003-02-14 17:12 ` Larry McVoy
2003-02-14 18:40 ` Roman Zippel
2003-02-14 18:44 ` Larry McVoy
2003-02-14 18:59 ` Roman Zippel
2003-02-15 11:34 ` Henning P. Schmiedehausen
2003-02-14 17:28 ` Alan Cox
2003-02-14 23:01 ` Steven Cole
2003-02-14 17:20 ` David Dillow
2003-02-14 20:52 ` 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=3E4C9FAA.FC8A2DC7@y12.doe.gov \
--to=dillowd@y12.doe.gov \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.