From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jyotisr5@googlemail.com>
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com
 [IPv6:2a00:1450:4010:c03::230])
 by dpdk.org (Postfix) with ESMTP id 57292688B
 for <dev@dpdk.org>; Tue,  5 Nov 2013 15:30:13 +0100 (CET)
Received: by mail-la0-f48.google.com with SMTP id ec20so2709586lab.35
 for <dev@dpdk.org>; Tue, 05 Nov 2013 06:31:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=0MigBVA/XAs6Ksr0qk2uN51X1ytgBslArTSxY/qvnH0=;
 b=cBgLDx6mtM8TE4/bPORnv9fRCF4+4/6HYMddd2z3es52xZPzWVnCZb9rtvXV8Gz6nO
 +m4+qcC4Zj8suRL/Z/apvnqycaTANRwRhnVsYQA2L8v0vt5R3OA9/EwMICs9ZHBOdHdb
 5+rRSwoee6RH1MP6OMUJAuvYyl2ha3NqRLASKgsA9TflbthxTml8ft7acsZNUuuui3iu
 +Q4R4mkxAMVVldAof8mHHrEwH4z0aM/r6QKe/JxtrQXLuQzvY75GtMp2hw5T41F9fIbF
 8ajagj5eWy9KJKJ+H9VTqectilrMKYOh3noAZNzP9JE99d61uH0WgATHkriKghbSB0va
 gJCg==
MIME-Version: 1.0
X-Received: by 10.152.143.6 with SMTP id sa6mr8372928lab.20.1383661866136;
 Tue, 05 Nov 2013 06:31:06 -0800 (PST)
Received: by 10.112.168.98 with HTTP; Tue, 5 Nov 2013 06:31:06 -0800 (PST)
In-Reply-To: <20131105122319.GA26200@debian>
References: <CAJn5u1mMHhg+k4ExoSCJinWUvBTXhkcJK=d9JXnSruFZ6e=HSg@mail.gmail.com>
 <20131105122319.GA26200@debian>
Date: Tue, 5 Nov 2013 20:01:06 +0530
Message-ID: <CAJn5u1m5wgm3XrNGCkpgQSnLeVeoTQ=BGJHuuATpuaZZmUSYhQ@mail.gmail.com>
From: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
To: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>,
 "dev@dpdk.org" <dev@dpdk.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-dev] pci_unbind.py failure
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 14:30:13 -0000

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
>