From: Kip Macy <kmacy@netapp.com>
To: nick@snowman.net
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Thu, 14 Jun 2001 14:37:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.10.10106141434260.6619-100000@orbit-fe.eng.netapp.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106141731030.16013-100000@ns>
So it would seem. Here is the polite message I received in response my
inquiry regarding the crypto interface to the card:
>
>
> Thank you for your inquiry. We do not offer the
> technical spec;s for the IPSec
> features of this NIC, due to the intellectual
> property-heavy nature of this
> product. We will, however, be releasing a Linux
> driver which supports this
> feature in the very near future under the beta
> section of our support site. The
> base driver for the 990 will be open source, the
> advanced driver (offloads,
> etc.) will not be open source. Hope that somewhat
> helps you.
On Thu, 14 Jun 2001 nick@snowman.net wrote:
> Erm, that is going to be a problem. Crypto benifits more from open source
> than any other market segment, and binary only drivers for linux are not
> the way to go. I guess I need to get rid of my 5-10 3cr990s and replace
> them with someone else's product?
> Nick
>
> On Thu, 14 Jun 2001, Kip Macy wrote:
>
> > IPsec support will be binary only.
> >
As I mentioned previously IP heavy is a euphemism for commodity.
next prev parent reply other threads:[~2001-06-14 21:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 0:24 3com Driver and the 3XP Processor Brent D. Norris
2001-06-12 0:29 ` Kip Macy
2001-06-12 0:43 ` Brent D. Norris
2001-06-12 1:18 ` Kip Macy
2001-06-12 16:24 ` Alan Cox
2001-06-12 16:12 ` Pavel Machek
2001-06-13 10:30 ` James Sutherland
2001-06-14 19:13 ` Brent D. Norris
2001-06-14 21:13 ` Martin Moerman
2001-06-14 21:18 ` nick
2001-06-14 21:26 ` Kip Macy
2001-06-14 21:32 ` nick
2001-06-14 21:37 ` Kip Macy [this message]
2001-06-15 2:50 ` Dr. Kelsey Hudson
2001-06-15 2:47 ` Dr. Kelsey Hudson
2001-06-15 2:51 ` nick
2001-06-15 4:01 ` [OT] " Brent D. Norris
2001-06-15 14:45 ` Alan Cox
2001-06-15 14:59 ` Venkatesh Ramamurthy
2001-06-17 16:35 ` Pavel Machek
2001-06-16 9:04 ` Martin Moerman
2001-06-14 21:37 ` David S. Miller
2001-06-14 21:40 ` nick
2001-06-14 21:40 ` Kip Macy
2001-06-14 21:41 ` David S. Miller
2001-06-15 15:12 ` Pete Wyckoff
2001-06-15 15:37 ` David S. Miller
2001-06-15 15:52 ` Pekka Pietikainen
2001-06-16 9:12 ` Martin Moerman
2001-06-18 14:43 ` Jamie Lokier
2001-06-25 15:42 ` Jes Sorensen
2001-06-14 21:45 ` David S. Miller
2001-06-14 21:48 ` Kip Macy
2001-06-14 21:51 ` David S. Miller
2001-06-25 15:45 ` Jes Sorensen
2001-06-12 16:27 ` Alan Cox
2001-06-12 2:27 Brent D. Norris
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=Pine.GSO.4.10.10106141434260.6619-100000@orbit-fe.eng.netapp.com \
--to=kmacy@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@snowman.net \
/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).