From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ns.mahan.org (unknown [67.116.10.138]) by dpdk.org (Postfix) with ESMTP id 17CC5B0C6 for ; Mon, 16 Jun 2014 20:34:30 +0200 (CEST) Received: from [192.168.1.58] (localhost [127.0.0.1]) (authenticated bits=0) by ns.mahan.org (8.14.5/8.14.5) with ESMTP id s5GIYf4F054030; Mon, 16 Jun 2014 11:34:42 -0700 (PDT) (envelope-from mahan@mahan.org) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <18573A5E-E333-4644-A15C-3B79357EAAAB@mahan.org> X-Mailer: iPad Mail (11D201) From: Patrick Mahan Date: Mon, 16 Jun 2014 11:34:40 -0700 To: Joubert Berger Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Writing a new 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: Mon, 16 Jun 2014 18:34:31 -0000 Joubert, By all means, look at the existing PMDs. It also helps if you have an exist= ing kernel driver to use/modify (preferably BSD based). That way you can hav= e a baseline to compare against. At least, that is method I used. Patrick > On Jun 13, 2014, at 9:08 AM, Joubert Berger wrote: >=20 > I am looking at writing a new driver for DPDK for a NIC that is currently > not supported. What is the best way to start this? Is the a porting > guide? Or should I look at existing drivers as examples? >=20 > --joubert