From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 781BB2946 for ; Sat, 9 Jul 2016 15:36:13 +0200 (CEST) Received: from cpe-2606-a000-111b-40ed-215-ff-fecc-4872.dyn6.twc.com ([2606:a000:111b:40ed:215:ff:fecc:4872] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1bLsP0-00035a-PJ; Sat, 09 Jul 2016 09:34:48 -0400 Date: Sat, 9 Jul 2016 09:34:27 -0400 From: Neil Horman To: "Mcnamara, John" Cc: Thomas Monjalon , "De Lara Guarch, Pablo" , "dev@dpdk.org" , "Richardson, Bruce" , Stephen Hemminger , Panu Matilainen Message-ID: <20160709133427.GA21705@neilslaptop.think-freely.org> References: <20160708121744.GA14917@hmsreliant.think-freely.org> <2459096.U0Mj9JPKfX@xps13> <20160708134214.GB14917@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Score: -1.0 (-) X-Spam-Status: No Subject: Re: [dpdk-dev] [PATCH] crypto: normalize cryptodev pmd names with macros X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2016 13:36:13 -0000 On Fri, Jul 08, 2016 at 07:03:10PM +0000, Mcnamara, John wrote: > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman > > Sent: Friday, July 8, 2016 2:42 PM > > To: Thomas Monjalon > > Cc: De Lara Guarch, Pablo ; dev@dpdk.org; > > Richardson, Bruce ; Stephen Hemminger > > ; Panu Matilainen > > Subject: Re: [dpdk-dev] [PATCH] crypto: normalize cryptodev pmd names with > > macros > > > > On Fri, Jul 08, 2016 at 02:40:01PM +0200, Thomas Monjalon wrote: > > > 2016-07-08 08:17, Neil Horman: > > > > I suppose thats fine, sure, though I'm really not comfortable with > > > > an open source project requiring what appears to be non-open source > > > > components (though I can't really tell what the snow3g or kasumi > > license is). > > > > > > Yes you're right. > > > IMHO, it is acceptable because it is free (just need a registration) > > > but it can be discussed. > > > I think there are some legal export issues because of crypto aim. > > Yeah, crypto usually has munitions export restrictions. I'm fine with > > that, as long as the license to the code is GPL. And I can't tell what > > the license is because you have to register to get it before you can see > > it. > > > > If you, or someone can confirm that the snow3g and kasumi ssl libraries > > are open source compatible (or better still if the license can be > > announced prior to registration on the web site), then I'm fine with it, > > and am happy to test with it, I just don't want to register without > > knowing that beforehand. > > Hi Neil, > > The license is "Intel Pre-Release Software License Agreement". We will send a > patch to make this this clear in the documentation. We will also see if it > can be made visible on the download page. > > I can send you a copy of the license if you wish. Pablo has already tested > compilation with the latest version of the patch. > I understand and appreciate that, but I'd still like to have a copy of the license. It seems a bit unreasonable to me to include open source drivers in an open source project, if they can't be built without a non-open source library included. Neil > John > >