From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49])
 by dpdk.org (Postfix) with ESMTP id 2188468CD
 for <dev@dpdk.org>; Wed,  3 Dec 2014 19:20:14 +0100 (CET)
Received: by mail-wg0-f49.google.com with SMTP id n12so12278526wgh.8
 for <dev@dpdk.org>; Wed, 03 Dec 2014 10:20:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=Zj7kW/nq/kr+M1TgQ8cvQxusHejmPpvhrXTUWvXX6W4=;
 b=X20lsM9cVIdWh0P6gnu9ULjX3bwgJDVjfORaTuyjdNwWMLNtNXcQgAu8L9gFWO9818
 ujihwSy4j2PCqx7liix9W7pDKrAvSUTIBQBWaIPfzjTiLKnvgrNNmcem3BnqkmFNhgre
 Ftz3HynNadS0yH5n1DNu1pHqoIO01IfbId4cbfcav1zotkEBktSr1rvupwskpzWsOmWM
 P4AFhmDr5eoM4xXaeLo/GAoOrul4N5aT8gnmtuVvFBzrDfWxfk4L14JIcrYsxiIc+JBH
 3vHyzgUp3SsRLOvrfcUrX0y0k8qJvZDA5T9NCAq+BZtmbiwpTH4nzy9YIwGt1diWJjjc
 J6+w==
X-Gm-Message-State: ALoCoQnp2QVX7owt7LBy05/lvZdkADJOar2WEyUd0ok3lmR907j6hRPnFeBlIBifyfQb6xWXanTx
X-Received: by 10.194.23.10 with SMTP id i10mr9221733wjf.11.1417630813916;
 Wed, 03 Dec 2014 10:20:13 -0800 (PST)
Received: from xps13.localnet (112.26.90.92.rev.sfr.net. [92.90.26.112])
 by mx.google.com with ESMTPSA id ej10sm12442450wib.1.2014.12.03.10.20.12
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 03 Dec 2014 10:20:13 -0800 (PST)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Zhang Haoyu <zhanghy@sangfor.com>
Date: Wed, 03 Dec 2014 19:19:39 +0100
Message-ID: <1548205.Kk2sct74qS@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.3 (Linux/3.17.4-1-ARCH; KDE/4.14.3; x86_64; ; )
In-Reply-To: <20141203100443.6518bb13@urahara>
References: <201412030948566609305@sangfor.com>
 <20141203100443.6518bb13@urahara>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 18:20:14 -0000

2014-12-03 10:04, Stephen Hemminger:
> On Wed, 3 Dec 2014 09:48:57 +0800
> "Zhang Haoyu" <zhanghy@sangfor.com> wrote:
> > I see that broadcom driver will be supported in DPDK-2.0 from 
> > DPDK roadmap(http://dpdk.org/dev/roadmap),
> > any details about the progress?
> 
> I have patch, just too big for mailing list.

Yes, a repository to maintain this broadcom driver should be open soon.
The goal is to merge it in DPDK 2.0 and to maintain it in a sub-repository
with a "pull request" model.

By the way, the sub-repository model will be also applied to i40e and to any
other driver having a maintainer who requests it.

-- 
Thomas