From: 張敬昊 <frank@csie.io>
To: stud4063294@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] No probed ethernet devices. Does DPDK support BCM57810?
Date: Fri, 1 Jun 2018 13:02:15 +0800 [thread overview]
Message-ID: <CA+vFTf-Vk4fHWxRHyDiddyE6Jhbp47nDecrkbVrcia-5myozrg@mail.gmail.com> (raw)
In-Reply-To: <CA+vFTf8iu1p=th-L0BUxH9QWt1kSqj3Yc7SrPfgMt_6jKWVsEg@mail.gmail.com>
Hi Wu,
After a deeper inspection into bnx2x_ethdev.c, I realized 0x168e is
actually on the list.
Is it possible that you didn't set CONFIG_RTE_LIBRTE_BNX2X_PMD=y in
config/common-base?
Try to recompile DPDK library with the above option enabled, perhaps
that'll solve your problem.
BR,
Frank
On Fri, Jun 1, 2018 at 12:20 PM 張敬昊 <frank@csie.io> wrote:
> Hi Wu,
>
> Please take a look at
> http://dpdk.org/doc/guides/nics/bnxt.html
> and
> http://dpdk.org/browse/dpdk/tree/drivers/net/bnxt/bnxt_ethdev.c#n95
>
> It appears that BCM57810 is not in the support list.
>
> BR,
> Frank
>
> On Fri, Jun 1, 2018 at 11:25 AM 伍英華 <stud4063294@gmail.com> wrote:
>
>> Hi,
>> I am using NIC Broadcom Corporation NetXtreme II BCM57810 10 Gigabit
>> Ethernet 168e.
>>
>> I bind igb_uio to the network device but got error when running testpmd:
>> ========
>> # ./testpmd -c 3 -n 4 -- -i
>> EAL: Detected 32 lcore(s)
>> EAL: Multi-process socket /var/run/.rte_unix
>> EAL: Probing VFIO support...
>> EAL: VFIO support initialized
>> testpmd: No probed ethernet devices
>> Interactive-mode selected
>> ...
>> ========
>>
>> Since the original driver is bnx2x, I checked the supported NIC:
>> http://dpdk.org/doc/guides/nics/bnx2x.html
>>
>> and the PCI devices this driver supports:
>>
>> http://dpdk.org/browse/dpdk-stable/tree/drivers/net/bnx2x/bnx2x_ethdev.c#n24
>>
>> I am confused that does DPDK support BCM57810 ? Or QLogic 578xx only?
>>
>> Regards,
>> Wu
>>
>
>
>
prev parent reply other threads:[~2018-06-01 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 3:25 伍英華
2018-06-01 4:20 ` 張敬昊
2018-06-01 5:02 ` 張敬昊 [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=CA+vFTf-Vk4fHWxRHyDiddyE6Jhbp47nDecrkbVrcia-5myozrg@mail.gmail.com \
--to=frank@csie.io \
--cc=stud4063294@gmail.com \
--cc=users@dpdk.org \
/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).