From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ognjen Joldzic <ognjen.joldzic@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 82546EB Copper issue
Date: Wed, 20 Nov 2013 08:57:03 +0100 [thread overview]
Message-ID: <2031360.6MEvh5xnbq@x220> (raw)
In-Reply-To: <CAArUB1gNjCScrPbmCS6QNwdWn7zPgddescyMOg+qfzNN+uX8Dw@mail.gmail.com>
Hello,
19/11/2013 23:44, Ognjen Joldzic :
> Recently I came across a 82546EB Dual-port Gigabit Ethernet (Copper) NIC
> and tried to include it in our current DPDK setup. However, the card
> doesn't seem to be supported (I was unable to bind the igb_uio driver).
> There was a post in mailing list earlier this year stating that this
> particular NIC is not supported as of r1.2.3.
> Is the situation any different with the 1.5.0 release (or are there any
> plans to support this model)?
The page http://dpdk.org/doc/nics says that 8254x should be supported.
But looking in details:
% grep 'RTE_PCI_DEV_ID_DECL.*8254' lib/librte_eal/common/include/rte_pci_dev_ids.h
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82540EM)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82545EM_COPPER)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82545EM_FIBER)
It means that only 82540 and 82545 are supported.
I don't know if there is a big difference with 82546 controller
and I'm not aware of any plan to support it.
So feel free to try and patch it.
--
Thomas
next prev parent reply other threads:[~2013-11-20 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 22:44 Ognjen Joldzic
2013-11-20 7:57 ` Thomas Monjalon [this message]
[not found] ` <CAArUB1iHoG7SVkRC6O1h0eWkEmiKjOtvN1ie04y4HJ7G=MzUBA@mail.gmail.com>
2013-11-22 8:55 ` Thomas Monjalon
2013-12-20 12:52 ` [dpdk-dev] [PATCH] pci: support 82546EB Thomas Monjalon
2014-01-02 15:08 ` Thomas Monjalon
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=2031360.6MEvh5xnbq@x220 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ognjen.joldzic@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).