From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f53.google.com (mail-pg0-f53.google.com [74.125.83.53]) by dpdk.org (Postfix) with ESMTP id 28AEF3DC for ; Sun, 18 Dec 2016 17:19:39 +0100 (CET) Received: by mail-pg0-f53.google.com with SMTP id p66so51544267pga.2 for ; Sun, 18 Dec 2016 08:19:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudsimple-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HaFgP8tvaQH4DRsnB6mnZ/cS7l/YLMRWX/wOzDTdk7E=; b=C6v1BBWYCn7cVb5cpktfPAS3NNAIU/iWhbCG5p0xgVhpEdE9FGt1izoBHL56W/s/7s k5IUCqQQPfyaUxYeyjWeP2yz9gXCj9Ri/F/LfODUlKc7BgAj7U0rjiFyf2P6I51Avz1T L3DG/uRq6kukv4vtivmtfuv3XoYT3+CR/VJR733UeVWzNVTiTzmGesrDsw/pJzziMYZc GU92fQzA4N9YWnb5QHLMGd1bKBRGF15jnFgTGRWLIBY+CrItoDakZw+xJmwB3HdCGPQj Iuoqcav3A2vvyyP1WkloSxuSlEojmdkCj13EOU1cCRUzGluL1JROOzSJfCF+lNUIeYf9 tODg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HaFgP8tvaQH4DRsnB6mnZ/cS7l/YLMRWX/wOzDTdk7E=; b=NrOtyA2Poqhe3PT7D8P0nqxX/jG52E8Gl4I+GqdrgjyADp2smNeo9KTTuGjeQjjFWS o89TKqiKfelB9wSNgqzKnSk4/sgEhfjigbCrINEzjt5g5ZVFFHQYhNWsTchwWcdyXXn3 C3v04odd1WR+paNkbA5O0bh/pxOFnzxosp7f+6WZvUsuQukqLriLLRJG/BbQagfOsAlC Ce5yS0qWwnHeRE+E6VwWT8pK3sgcSbB115Zudqg3Z8a5cdZAd7ZYZsPCwZIjMI5vgOGI FZ9+kGjGlQeO3E+99hnUCZ+7m801O+5tgWxHZb2AGNb9DqWNX5cvBM4+HkWQEcEU/dgS QasQ== X-Gm-Message-State: AKaTC01FLx2nLuxHezLGDdeem5D+5nupmdkmtV2jnUgf/EAvlSFX8/EQhDtc8Prc5iTXQAff X-Received: by 10.84.129.34 with SMTP id 31mr27041785plb.104.1482077978422; Sun, 18 Dec 2016 08:19:38 -0800 (PST) Received: from [192.168.1.34] ([117.208.186.21]) by smtp.gmail.com with ESMTPSA id v1sm25356154pgv.33.2016.12.18.08.19.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Dec 2016 08:19:38 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: Kumaraparameshwaran Rathnavel X-Mailer: iPhone Mail (14B100) In-Reply-To: Date: Sun, 18 Dec 2016 21:49:31 +0530 Cc: "users@dpdk.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <1394E9B2-BED1-49DA-A14E-EB5257E26F9E@cloudsimple.com> To: "Wiles, Keith" 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 16:19:39 -0000 Thanks Keith. I will make the change and let u know about it.=20 Thanking you, Param. > On 18-Dec-2016, at 9:05 PM, Wiles, Keith wrote: >=20 >=20 >> 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 a= nd library path of the DPDK. It is not able to find any pci devices during r= te_eal_pci_init. I am not getting any Network devices but when I use DPDKs e= xample Makefile I am able get the devices. What should be the reason for thi= s as in both cases the function is the same. >=20 > 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 o= n to the end of the link line including the drivers. The drivers do not use a= strong compiler link to be included in the image. What happens is the rte.a= pp.mk will include the drivers and the use constructor calls to bind to DPDK= . >=20 > I hope that is clearer. One way to add a driver is to include its .o on th= e link line of your makefile or try using the examples directory style of Ma= kefile in your application. >=20 >>=20 >> Thanking you, >> Param. >>=20 >=20 > Regards, > Keith >=20