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 1919E4C6E for ; Wed, 31 Jul 2013 23:23:18 +0200 (CEST) Received: from [192.168.71.30] (localhost [127.0.0.1]) (authenticated bits=0) by ns.mahan.org (8.14.5/8.14.5) with ESMTP id r6VLNecH067261 for ; Wed, 31 Jul 2013 14:23:40 -0700 (PDT) (envelope-from mahan@mahan.org) From: Patrick Mahan Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (10B329) Message-Id: <1486472B-BF17-4A85-887A-806E6DB32480@mahan.org> Date: Wed, 31 Jul 2013 14:23:40 -0700 To: dev@dpdk.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: [dpdk-dev] Question regarding PMDs 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: Wed, 31 Jul 2013 21:23:19 -0000 Okay, I wadding into the process of writing a poll-mode driver for DPDK.=20 First question, is the use of the UIO device a requirement (outside of the n= eed for interrupt support) since it is possible to map the PCI bars via /dev= /mem? Second question, is it expected that the NIC hardware would already have bee= n initialized by the kernel driver for that device? Say to load microcode on= an intelligent NIC? I am sure to have more when the water level gets above my head ;-) Thanks, Patrick=20=