From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) by dpdk.org (Postfix) with ESMTP id 18024156 for ; Wed, 20 Nov 2013 08:55:02 +0100 (CET) Received: by mail-we0-f175.google.com with SMTP id p61so4166081wes.34 for ; Tue, 19 Nov 2013 23:55:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=QpWV1SsRT7D271r1Lsp7HisCEDYmsjtf7PHuJHIE8p8=; b=e5fqnKKRvnCiVP5jDTEAf9NzMhADMUd4Gq++K9pO6H8y/Fj5N5g/UdD/ifFJY4qChb 51S/JpLF6byS4Y6E05lgbkiGxydyBLfljH6FUIUdH3q0QWT4Fwiyev3PKHP0AgKyPSZ+ FB3bolAMLg/Mr9/8sZyqqYJcxi8Go3Z0cV9VcVljIB6MHhobJwj7IIEUWNSqKLyDtUtl lyH4G+t+uFXCNa/7mxSnnHdOysF/xDrZ8Yq7VBnwVu5rlo/4Swaa6j2cvpqWOuDA31Jj 38tNauCrCv+43NxEk/ArjhqfVGpi5lMwvkQaWDN+HWK+6JAIYdqomJO4A+cQZmyeADUb WKBg== X-Gm-Message-State: ALoCoQlXcBRZPh5XFop5gl3m2aszUr90DJr8lLachoeivtJWALPapmqDwxoVyp4mzdwazn0NFKJr X-Received: by 10.194.122.99 with SMTP id lr3mr23909387wjb.21.1384934159652; Tue, 19 Nov 2013 23:55:59 -0800 (PST) Received: from x220.localnet (abo-107-62-68.mts.modulonet.fr. [85.68.62.107]) by mx.google.com with ESMTPSA id s2sm13412631wiy.7.2013.11.19.23.55.58 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2013 23:55:58 -0800 (PST) From: Thomas Monjalon To: Ognjen Joldzic Date: Wed, 20 Nov 2013 08:57:03 +0100 Message-ID: <2031360.6MEvh5xnbq@x220> Organization: 6WIND User-Agent: KMail/4.11.2 (Linux/3.11.4-1-ARCH; KDE/4.11.2; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] 82546EB Copper issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2013 07:55:02 -0000 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