From: Stephen Hemminger <stephen@networkplumber.org>
To: Keren Hochman <keren.hochman@lightcyber.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] support BCM5719 driver
Date: Tue, 30 Aug 2016 07:47:50 -0700 [thread overview]
Message-ID: <20160830074750.247ac6ab@xeon-e3> (raw)
In-Reply-To: <59DD23F5-7052-44D0-B005-74C397AB3332@lightcyber.com>
On Tue, 30 Aug 2016 13:54:41 +0300
Keren Hochman <keren.hochman@lightcyber.com> wrote:
> Hi,
>
> I tried to bind BCM5719 driver to DPDK compatible driver: (I tried both to uio_pci_generic and igb_uio)
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:03:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe' drv=uio_pci_generic unused=tg3,igb_uio
> 0000:03:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe' drv=igb_uio unused=tg3,uio_pci_generic
>
> But when I ran from the dpdk example: link_status_interrupt I received an error No ethernet port.
>
> (When I tried to bind I350 Gigabit Network Connection it worked.
>
> Thank you, Keren
>
The BCM5719 device is not supported by the current DPDK driver.
Only the 10G Broadcom NetExtreme II devices are supported.
prev parent reply other threads:[~2016-08-30 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 10:54 Keren Hochman
2016-08-30 14:47 ` Stephen Hemminger [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=20160830074750.247ac6ab@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=keren.hochman@lightcyber.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).