From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 3427D2C5E for ; Sun, 18 Dec 2016 16:35:32 +0100 (CET) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP; 18 Dec 2016 07:35:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,369,1477983600"; d="scan'208";a="43809351" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga005.jf.intel.com with ESMTP; 18 Dec 2016 07:35:31 -0800 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.68]) by FMSMSX105.amr.corp.intel.com ([169.254.4.250]) with mapi id 14.03.0248.002; Sun, 18 Dec 2016 07:35:30 -0800 From: "Wiles, Keith" To: Kumaraparameshwaran Rathnavel CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Network Devices Thread-Index: AQHSWPQ/ynwJfBN2MkSEZP2CqYW0/qEOXOyA Date: Sun, 18 Dec 2016 15:35:29 +0000 Message-ID: References: <1394E9B2-BED1-49DA-A14E-EB5257E26F9E@cloudsimple.com> In-Reply-To: <1394E9B2-BED1-49DA-A14E-EB5257E26F9E@cloudsimple.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.128.108] Content-Type: text/plain; charset="us-ascii" Content-ID: <284024DAF7E0E64C8B9C3CC906517C4B@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Network Devices X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2016 15:35:32 -0000 > On Dec 18, 2016, at 12:01 AM, Kumaraparameshwaran Rathnavel wrote: >=20 > Hi All, >=20 > I am writing my own application and in Makefile I just use include files = and library path of the DPDK. It is not able to find any pci devices during= rte_eal_pci_init. I am not getting any Network devices but when I use DPDK= s example Makefile I am able get the devices. What should be the reason for= this as in both cases the function is the same. The makefiles in the DPDK examples include DPDK make fragment files *.mk, t= hese files include the mk/rte.app.mk fragment and it appends the libraries = on to the end of the link line including the drivers. The drivers do not us= e a strong compiler link to be included in the image. What happens is the r= te.app.mk will include the drivers and the use constructor calls to bind to= DPDK. I hope that is clearer. One way to add a driver is to include its .o on the= link line of your makefile or try using the examples directory style of Ma= kefile in your application. >=20 > Thanking you, > Param. >=20 Regards, Keith