DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
To: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] pci_unbind.py failure
Date: Tue, 5 Nov 2013 20:01:06 +0530	[thread overview]
Message-ID: <CAJn5u1m5wgm3XrNGCkpgQSnLeVeoTQ=BGJHuuATpuaZZmUSYhQ@mail.gmail.com> (raw)
In-Reply-To: <20131105122319.GA26200@debian>

Thanks for the quick reply. I saw some definitions of e1000_phy_82579 hence
I thought (hoped) the NIC would be supported. I will try to run my dpdk app
inside a VM with an emulated e1000 NIC (just to test the code ..).

Thanks





On Tue, Nov 5, 2013 at 5:53 PM, Cyril Cressent <cyril.cressent@intel.com>wrote:

> On Tue, Nov 05, 2013 at 05:41:17PM +0530, Jyotiswarup Raiturkar wrote:
> >
> > I have 82579LM NIC which i'm trying to bind to the igb_uio driver. I get
> > the following error
>
> I can't find the 82579LM listed on
> http://dpdk.org/doc/nics
> or in
> lib/librte_eal/common/include/rte_pci_dev_ids.h
>
> My guess is that your NIC is not supported.
>
> > My kernel version is 3.5.0-23-generic ( Ubuntu 12.04.2 LTS). I heard
> about
> > an UIO bug in 3.10; is this the same bug i;m hitting?
>
> No, the bug you mention prevented the correct registration of the second
> and subsequent ports bound to igb_uio. The first port bound to igb_uio
> was working fine.
>
> Cyril
>

  reply	other threads:[~2013-11-05 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 12:11 Jyotiswarup Raiturkar
2013-11-05 12:23 ` Cyril Cressent
2013-11-05 14:31   ` Jyotiswarup Raiturkar [this message]
2013-11-05 16:04     ` Cyril Cressent
2013-11-13 11:17       ` Jyotiswarup Raiturkar
2013-11-13 11:27         ` Jose Gavine Cueto
2013-11-13 11:36           ` Daniel Kaminsky
2013-11-13 14:57             ` Vladimir Medvedkin
2013-11-13 15:00               ` Jyotiswarup Raiturkar
2013-11-13 16:16                 ` Jose Gavine Cueto

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='CAJn5u1m5wgm3XrNGCkpgQSnLeVeoTQ=BGJHuuATpuaZZmUSYhQ@mail.gmail.com' \
    --to=jyotisr5@googlemail.com \
    --cc=dev@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).