DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Srinivasreddy R <srinivasreddy4390@gmail.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk-16.07 : Does dpdk supports BCM5720
Date: Tue, 21 Mar 2017 09:18:13 -0500	[thread overview]
Message-ID: <CACZ4nhtBuzkTm+A=O9n=YpPZ26MrTcFABDZ=pZ1tkfCAdzWr9A@mail.gmail.com> (raw)
In-Reply-To: <CAJP4VWhEZ+n=HCx=JfCpNNEHWcUsXq_htLT0_zHwB0HKEHvs_Q@mail.gmail.com>

Yes. That is right Srinivas.

Ferruh, thanks for pointing to the supported device list.

Thanks
-Ajit

On Tue, Mar 21, 2017 at 6:36 AM, Srinivasreddy R <
srinivasreddy4390@gmail.com> wrote:

> Thank you so much for your quick reply .
>
>
> On Tue, Mar 21, 2017 at 4:40 PM, Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
>
>> On 3/21/2017 11:01 AM, Srinivasreddy R wrote:
>> > Hi all,
>> > I have "NetXtreme BCM5720 Gigabit Ethernet PCI" controllers .
>> > I have binded to igb_uio . I have run l2fwd example .l2fwd saysno ports
>> bye
>> > .
>> > Does BCM5720 works with dpdk .
>>
>> Is your device's PCI device ID listed in the driver:
>> http://dpdk.org/browse/dpdk-stable/tree/drivers/net/bnxt/bnx
>> t_ethdev.c?h=v16.07.2#n72
>>
>> my device's PCI device is ( BCM5720 ) is not listed in the above link .
> so i conform it is not supported .
>
>> >
>> > ./dpdk-stable-16.07.2/tools/dpdk-devbind.py --status
>> >
>> > Network devices using DPDK-compatible driver
>> > ============================================0000:02:00.0 'NetXtreme
>> > BCM5720 Gigabit Ethernet PCIe' drv=igb_uio unused=
>> > 0000:02:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe' drv=igb_uio
>> unused=
>> > Network devices using kernel driver
>> > ===================================
>> > 0000:01:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe' if=em1 drv=tg3
>> > unused=igb_uio *Active*
>> > 0000:01:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe' if=em2 drv=tg3
>> > unused=igb_uio
>> >
>> > Other network devices
>> > =====================
>> > <none>
>> >
>> > ************************************************************
>> *********************************************
>> >
>> >
>> > examples/l2fwd# ./build/app/l2fwd -c 0xf -m 1024 -n 3 -- -p 0x3
>> > EAL: Detected 16 lcore(s)
>> > EAL: No free hugepages reported in hugepages-1048576kB
>> > EAL: Probing VFIO support...
>> > PMD: bnxt_rte_pmd_init() called for (null)EAL: Error - exiting with
>> code: 1
>> >   Cause: No Ethernet ports - bye
>> >
>> >
>> > Document says :
>> >
>> >
>> > *Broadcom NetXtreme-C®/NetXtreme-E® BCM5730X and BCM5740X family of
>> > Ethernet Network Controllers*
>> >
>> > thanks
>> > srinivas
>> >
>>
>> thanks
> srinivas
>

      reply	other threads:[~2017-03-21 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 11:01 Srinivasreddy R
2017-03-21 11:10 ` Ferruh Yigit
2017-03-21 11:36   ` Srinivasreddy R
2017-03-21 14:18     ` Ajit Khaparde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACZ4nhtBuzkTm+A=O9n=YpPZ26MrTcFABDZ=pZ1tkfCAdzWr9A@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=srinivasreddy4390@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).