From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id F12D37EB0 for ; Thu, 4 Dec 2014 03:58:25 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 03 Dec 2014 18:58:24 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,512,1413270000"; d="scan'208";a="632400777" Received: from pgsmsx105.gar.corp.intel.com ([10.221.44.96]) by fmsmga001.fm.intel.com with ESMTP; 03 Dec 2014 18:58:23 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by pgsmsx105.gar.corp.intel.com (10.221.44.96) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 4 Dec 2014 10:58:15 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.110]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.5]) with mapi id 14.03.0195.001; Thu, 4 Dec 2014 10:58:14 +0800 From: "Qiu, Michael" To: Thomas Monjalon , Zhang Haoyu Thread-Topic: [dpdk-dev] [question] DPDK-2.0 support broadcom driver Thread-Index: AQHQDpty+9Ci/561CEWw/9egBGJ5jw== Date: Thu, 4 Dec 2014 02:58:13 +0000 Message-ID: <533710CFB86FA344BFBF2D6802E60286C9C8DE@SHSMSX101.ccr.corp.intel.com> References: <201412030948566609305@sangfor.com> <20141203100443.6518bb13@urahara> <1548205.Kk2sct74qS@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [question] DPDK-2.0 support broadcom driver 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: Thu, 04 Dec 2014 02:58:26 -0000 On 12/4/2014 3:18 AM, Thomas Monjalon wrote:=0A= > 2014-12-03 10:04, Stephen Hemminger:=0A= >> On Wed, 3 Dec 2014 09:48:57 +0800=0A= >> "Zhang Haoyu" wrote:=0A= >>> I see that broadcom driver will be supported in DPDK-2.0 from =0A= >>> DPDK roadmap(http://dpdk.org/dev/roadmap),=0A= >>> any details about the progress?=0A= >> I have patch, just too big for mailing list.=0A= > Yes, a repository to maintain this broadcom driver should be open soon.= =0A= > The goal is to merge it in DPDK 2.0 and to maintain it in a sub-repositor= y=0A= > with a "pull request" model.=0A= >=0A= > By the way, the sub-repository model will be also applied to i40e and to = any=0A= > other driver having a maintainer who requests it.=0A= =0A= This is cool, "pull request" model will be much more efficient for DPDK.= =0A= =0A= Then we would have a maintainer list.=0A= =0A= Thanks,=0A= Michael=0A= >=0A= =0A=