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 F0555282 for ; Fri, 17 Feb 2017 23:49:20 +0100 (CET) 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 1cerKu-0008D7-Im; Fri, 17 Feb 2017 17:49:10 -0500 Date: Fri, 17 Feb 2017 17:48:13 -0500 From: Neil Horman To: Vincent JARDIN Cc: Bruce Richardson , Ferruh Yigit , Hemant Agrawal , dev@dpdk.org, thomas.monjalon@6wind.com, shreyansh.jain@nxp.com, john.mcnamara@intel.com, jerin.jacob@caviumnetworks.com Message-ID: <20170217224813.GA8861@neilslaptop.think-freely.org> References: <1485172803-17288-1-git-send-email-hemant.agrawal@nxp.com> <1487205586-6785-1-git-send-email-hemant.agrawal@nxp.com> <20170216132249.GA18056@hmswarspite.think-freely.org> <20170216132751.GA100024@bricha3-MOBL3.ger.corp.intel.com> <20170217121358.GA135568@bricha3-MOBL3.ger.corp.intel.com> <8479045a-fb1c-78c9-cfde-a669633249e8@6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8479045a-fb1c-78c9-cfde-a669633249e8@6wind.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-Spam-Score: -2.9 (--) X-Spam-Status: No Subject: Re: [dpdk-dev] [PATCHv7 00/47] NXP DPAA2 PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 22:49:21 -0000 On Fri, Feb 17, 2017 at 01:17:26PM +0100, Vincent JARDIN wrote: > Le 17/02/2017 à 13:13, Bruce Richardson a écrit : > > If it builds without an SDK dependency I'd be happy enough to see this > > merged into DPDK. > > +1, the patch is clean enough to be compiled. > > Boards or CPUs can rely on specific SDK, firmware, etc., it is up to the > vendors. > I absolutely disagree with this. Its completely anathema to the reason open source code is beneficial to the community that maintains it. By allowing code like this into the project, you've tacitly agree to do regular maintenence on their code for them, without the reciprocating benefit of being able to use their hardware free of additional license terms. If you want to have a non-open driver that works with an open source project, thats fine, but keep it out of tree, and maintain it yourself. What you've esentially asked for here is for the dpdk community to be some free labor, when APIS and such change. No thank you. I re-iterate my NAK. > regards, > Vincent >