From: Ion Badulescu <ionut@badula.org>
To: James Williams <fido@tcob1.net>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: 3Comm 3CR990-TX-97 NIC
Date: Mon, 3 Feb 2003 11:16:58 -0500 [thread overview]
Message-ID: <200302031616.h13GGwwm005678@buggy.badula.org> (raw)
In-Reply-To: <3E3DF2A5.7060504@pobox.com>
On Sun, 02 Feb 2003 23:40:05 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
>
> There are two Linux drivers for it. One is 3com's, a bit shoddy but Ion
> B. did a nice job of cleaning it up. The other is David Dillow's; DD's
> driver looks really good, supports NAPI and all sorts of bells and whistles.
>
> I'm currently waiting to see if DD's driver gets the stamp of approval
> from a certain legal department. If that doesn't come through soon, the
> "backup plan" kicks into effect, and Ion's cleanup of 3com's driver gets
> merged.
In the mean time, you can get my cleaned up version from
<http://www.badula.org/3c990/>. The 2.5 patch might not apply anymore
to the latest and greatest; let me know if that's indeed the case so
I can generate a new one.
> Neither driver hooks into the 2.5.x CryptoAPI, AFAIK...
Correct as far as the 3Com driver is concerned: it doesn't implement any
crypto stuff, I have no docs for it, and no free driver (OpenBSD in
particular) implements any of that stuff either.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
prev parent reply other threads:[~2003-02-03 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 1:18 3Comm 3CR990-TX-97 NIC James Williams
2003-02-03 4:40 ` Jeff Garzik
2003-02-03 16:16 ` Ion Badulescu [this message]
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=200302031616.h13GGwwm005678@buggy.badula.org \
--to=ionut@badula.org \
--cc=fido@tcob1.net \
--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