From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Helmut Sim <simhelmut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: fail to bind '82541GI Gigabit Ethernet Controller' to IGB_UIO driver
Date: Wed, 14 May 2014 16:45:36 +0200 [thread overview]
Message-ID: <1490308.sncVW4PuBc@xps13> (raw)
In-Reply-To: <CAF8yGaGn_fjhPRYVVy_q5zv4SVpoR9uWKSoNP7atj3NK1Ru0=g@mail.gmail.com>
Hi,
2014-05-14 17:27, Helmut Sim:
> unlike previous cases I went over in this forum, this NIC supposed to be
> supported (or maybe i read it incorrectly???):
>
> # cat lib/librte_eal/common/include/rte_pci_dev_ids.h | grep 82541GI
> #define E1000_DEV_ID_82541GI 0x1076
> #define E1000_DEV_ID_82541GI_LF 0x107C
> #define E1000_DEV_ID_82541GI_MOBILE 0x1077
This device is known but not supported.
You should use
# 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)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82546EB_COPPER)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82546EB_FIBER)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82546EB_QUAD_COPPER)
The dedicated page for this information is:
http://dpdk.org/doc/nics
You should try to enable this device in the code and see what happens.
Maybe that its support is straightforward.
Thanks for reporting
--
Thomas
next prev parent reply other threads:[~2014-05-14 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 14:27 fail to bind '82541GI Gigabit Ethernet Controller' to IGB_UIO driver Helmut Sim
2014-05-14 14:45 ` Thomas Monjalon [this message]
2014-05-14 14:53 ` Helmut Sim
[not found] ` <CAF8yGaESSVX2gyZwbnFjvG1t_Y9Ormx8rBJXxghStjHb64VqZg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-14 15:44 ` Helmut Sim
[not found] ` <CAF8yGaGYsYHR4761UCn0379dY2QB-GBP2_XBFCTb5XOGsTN9sg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-15 22:15 ` Thomas Monjalon
2014-05-18 14:07 ` Helmut Sim
2014-05-19 15:12 ` 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=1490308.sncVW4PuBc@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=simhelmut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).