Message-ID: <3E1C94C5.6FB0EFBD@y12.doe.gov>
Date: Wed, 08 Jan 2003 16:14:45 -0500
From: David Dillow <dillowd@y12.doe.gov>
Organization: BWXT Y-12/TC/UT Subcon/What a mess!
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: 3CR990 question (Nearly unrelated to iSCSI)
References: <200301081950.h08JoTr15738@buggy.badula.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1114
Lines: 30

Ion Badulescu wrote:
> Actually, the 3Com driver I cleaned up does not have support for the
> hardware crypto chip. Maybe the other driver you were referring to
> supports it?

Yes, and no. It doesn't support it in the version I sent to Jeff. I do
have code that uses it, and a kludge to use it under 2.4. As for 2.5, I
hope to work to get it supported with the IPSEC code properly.

I do support the other offloading it will do -- VLAN, Checksum, and TCP
segmentation.

> > I hope we will see it appear in a kernel RSN
> 
> Indeed. :) That damn legalese in 3Com's license...

And government work! I've got the paperwork in progress, should be RSN
as Jeff said. Word is no later than next Wednesday, though I'm pushing
for Friday.

I've got the firmware under a BSD style license that will work for us,
and the driver is completely GPL.

Dave Dillow
dillowd@y12.doe.gov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/