From: William Tu <u9012063@gmail.com>
To: dev@dpdk.org
Cc: pallavi.kadam@intel.com, Dmitry.Kozliuk@gmail.com,
ranjit.menon@intel.com
Subject: [dpdk-dev] [kmods PATCH v1] windows/netuio: add Intel e1000 device IDs
Date: Mon, 11 Oct 2021 11:49:02 -0700 [thread overview]
Message-ID: <20211011184902.1442-1-u9012063@gmail.com> (raw)
Add Intel Ethernet e1000 device IDs to netuio inf file.
Signed-off-by: William Tu <u9012063@gmail.com>
--
DPDK patch at:
http://inbox.dpdk.org/dev/20211007202451.90271-1-u9012063@gmail.com/T/#t
---
windows/netuio/netuio.inf | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/windows/netuio/netuio.inf b/windows/netuio/netuio.inf
index 816ff17c7936..28cd0be9de81 100644
--- a/windows/netuio/netuio.inf
+++ b/windows/netuio/netuio.inf
@@ -29,6 +29,7 @@ HKR,,Icon,,-5
[Standard.NT$ARCH$]
%netuio.DeviceDesc%=netuio_Device, Root\netuio
%netuio.nvme.DeviceDesc%=netuio_Device, PCI\CC_010802
+%Intel.F1521.Description%=netuio_Device, PCI\VEN_8086&DEV_1521
%Intel.F1572.Description%=netuio_Device, PCI\VEN_8086&DEV_1572
%Intel.F1580.Description%=netuio_Device, PCI\VEN_8086&DEV_1580
%Intel.F1581.Description%=netuio_Device, PCI\VEN_8086&DEV_1581
@@ -43,6 +44,7 @@ HKR,,Icon,,-5
%Intel.F101F.Description%=netuio_Device, PCI\VEN_8086&DEV_101F
%Intel.F104F.Description%=netuio_Device, PCI\VEN_8086&DEV_104F
%Intel.F104E.Description%=netuio_Device, PCI\VEN_8086&DEV_104E
+%Intel.F10D3.Description%=netuio_Device, PCI\VEN_8086&DEV_10D3
%Intel.F1591.Description%=netuio_Device, PCI\VEN_8086&DEV_1591
%Intel.F1592.Description%=netuio_Device, PCI\VEN_8086&DEV_1592
%Intel.F1593.Description%=netuio_Device, PCI\VEN_8086&DEV_1593
@@ -100,6 +102,7 @@ ClassName = "Windows UIO"
DiskName = "DPDK netUIO Installation Disk"
netuio.DeviceDesc = "netuio Device"
netuio.nvme.DeviceDesc = "netuio NVM Express Controller"
+Intel.F1521.Description = "Intel(R) I350 Gigabit Network Connection"
Intel.F1572.Description = "Intel(R) Ethernet Controller X710 for 10GbE SFP+"
Intel.F1580.Description = "Intel(R) Ethernet Controller XL710 for 40GbE backplane"
Intel.F1581.Description = "Intel(R) Ethernet Controller X710 for 10GbE backplane"
@@ -114,6 +117,7 @@ Intel.F15FF.Description = "Intel(R) Ethernet Controller X710 for 10GBASE-T"
Intel.F101F.Description = "Intel(R) Ethernet Controller V710 for 5GBASE-T"
Intel.F104F.Description = "Intel(R) Ethernet Controller X710 for 10 Gigabit backplane"
Intel.F104E.Description = "Intel(R) Ethernet Controller X710 for 10 Gigabit SFP+"
+Intel.F10D3.Description = "Intel(R) 82574L Gigabit Ethernet Controller"
Intel.F1591.Description = "Intel(R) Ethernet Controller E810-C for backplane"
Intel.F1592.Description = "Intel(R) Ethernet Controller E810-C for QSFP"
Intel.F1593.Description = "Intel(R) Ethernet Controller E810-C for SFP"
--
2.33.0.windows.2
next reply other threads:[~2021-10-11 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 18:49 William Tu [this message]
2021-10-12 1:54 ` Dmitry Kozlyuk
2021-10-12 3:31 ` Kadam, Pallavi
2021-10-19 19:01 ` [dpdk-dev] [kmods PATCH v2] windows/netuio: add Intel device ID William Tu
2021-11-24 16:11 ` William Tu
2022-01-11 14:21 ` [dpdk-dev] " 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=20211011184902.1442-1-u9012063@gmail.com \
--to=u9012063@gmail.com \
--cc=Dmitry.Kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
/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).