From: Chris Friesen via Intel-wired-lan <intel-wired-lan@osuosl.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] is there a way other than PCI IDs to distinguish E810 from E825/E830?
Date: Mon, 9 Mar 2026 12:37:55 -0600 [thread overview]
Message-ID: <04025549-91a4-47a8-b874-eaeb35a429bd@windriver.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi,
I've got an odd issue. We've got a request to use the in-tree ice
driver for the "legacy" NICs like the E810, and the out-of-tree ice
driver for the newer NICs associated with the Granite Rapids-D (E825/E830).
Is there any way to distinguish between these other than the PCI device
IDs? I'd rather not need to maintain a list of devices and need to
update them every time a new NIC variant comes out.
Thanks,
Chris
[-- Attachment #2: Type: text/html, Size: 669 bytes --]
next reply other threads:[~2026-03-09 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 18:37 Chris Friesen via Intel-wired-lan [this message]
2026-03-12 16:17 ` [Intel-wired-lan] is there a way other than PCI IDs to distinguish E810 from E825/E830? Przemek Kitszel
2026-03-12 20:24 ` Dawid Osuchowski
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=04025549-91a4-47a8-b874-eaeb35a429bd@windriver.com \
--to=intel-wired-lan@osuosl.org \
--cc=anthony.l.nguyen@intel.com \
--cc=chris.friesen@windriver.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=przemyslaw.kitszel@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