From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1563] Many I219 variants not supported by E1000 druver
Date: Fri, 11 Oct 2024 17:07:48 +0000 [thread overview]
Message-ID: <bug-1563-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1563
Bug ID: 1563
Summary: Many I219 variants not supported by E1000 druver
Product: DPDK
Version: 24.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
There are many variants of e1000 which are supported by Linux and FreeBSD
kernel drivers which are not handled by the DPDK e1000 PMD. Looks like the base
code for e1000 has not been updated in years.
Specifically, the Tiger Lake and related chips are not supported.
This interface would be useful for testing on my machine.
$ lspci -n -v -s 00:1f.6
00:1f.6 0200: 8086:15fc (rev 20)
DeviceName: Onboard - Ethernet
Subsystem: 1458:1000
Flags: bus master, fast devsel, latency 0, IRQ 226, IOMMU group 16
Memory at 88700000 (32-bit, non-prefetchable) [size=128K]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
$ sudo ethtool -i eno2
driver: e1000e
version: 6.10.11-amd64
firmware-version: 0.6-4
expansion-rom-version:
bus-info: 0000:00:1f.6
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3416 bytes --]
reply other threads:[~2024-10-11 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1563-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).