From: David Dillow <dillowd@y12.doe.gov>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3COM 3C990 NIC
Date: Tue, 22 Oct 2002 10:53:26 -0400 [thread overview]
Message-ID: <3DB56666.74ADDCB2@y12.doe.gov> (raw)
In-Reply-To: 3DB51EA2.5060106@pobox.com
Jeff Garzik wrote:
>
> David Dillow wrote:
> > I have a completely reworked version that I expect to be able to release RSN.
> > (I know, I know, some of you have heard that before... it just takes time to
> > get people around here to sign off on these things. :/)
> Will you be submitting this for inclusion in the kernel?
Yes, I plan to run it by you first, and then once it is in shape, have it
included. 3Com has agreed to release their firmware binary under a BSD license
so that we can include it. (No source code, unfortunately.)
> And, what differences exists between the 3c59x and 3c90x hardware, and
> 3c990? Just IPSEC?
Not really sure, ethernet hardware wise -- the driver communicates with an
onboard ARM chip, which we have to load firmware for. We then communicate with
it via several rings for commands, Tx packets, Rx packets, etc. There is an
onboard random number generator and crypto chip. We never drive the real
hardware directly, just talk to the firmware, which still has a few issues
that I am working with 3Com to resolve.
The nice thing about the firmware setup is that we don't really care which
card in the 3c990 family we're talking to per se -- they can change the
hardware all they want, and the driver should just work as long as we have
recent firmware. I currently support every version I know about:
3C990-{TX,SVR,B,M}-{,95,97}.
To set a date for this current vaporware -- I expect to have it to before the
end of November, and potentially much sooner. We have a conference just after
Thanksgiving, and our sponsors are itching to be able to say to those
attending that we've published this.
Dave
next prev parent reply other threads:[~2002-10-22 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 4:49 3COM 3C990 NIC Christopher Keller
2002-10-22 4:54 ` David Dillow
2002-10-22 9:47 ` Jeff Garzik
2002-10-22 14:53 ` David Dillow [this message]
2002-10-22 14:37 ` Christopher Keller
2002-10-22 23:13 ` David S. Miller
2002-10-23 3:50 ` David Dillow
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=3DB56666.74ADDCB2@y12.doe.gov \
--to=dillowd@y12.doe.gov \
--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