From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Chris Friesen <chris.friesen@windriver.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] is there a way other than PCI IDs to distinguish E810 from E825/E830?
Date: Thu, 12 Mar 2026 21:24:59 +0100 [thread overview]
Message-ID: <de5cc621-7ff1-446f-9700-f342b0527fb0@linux.intel.com> (raw)
In-Reply-To: <04025549-91a4-47a8-b874-eaeb35a429bd@windriver.com>
On 2026-03-09 7:37 PM, Chris Friesen via Intel-wired-lan wrote:
> Hi,
Hello Chris,
Thank you for your message. Given I'm from the more customer facing wing
I'll try to answer / guide you towards a path satisfactory for you. As
Przemek pointed out this is a mailing list for the upstream / in-tree
development side of things.
> 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).
As Przemek noted, our general recommendation is not to mix drivers
within the same system. That would mean using all in-tree drivers or all
OOT drivers.
The following scenarios:
1. all in-tree drivers (in-tree ice, in-tree iavf, in-tree irdma),
2. all OOT drivers (OOT ice, OOT iavf, OOT irdma).
are supported and validated.
A configuration like (and any combination similar to it):
* OOT ice, in-tree iavf, in-tree irdma
is not validated by Intel and certainly not recommended or supported. It
might work, but we are unable to help in case you run into issues using
such a setup.
> 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.
I think I know what you are trying to do here, please correct me if I'm
wrong.
You would like to pin a specific device like e.g. E810 to the in-tree
driver and the E825/E830 to the OOT driver.
If that's the case, then I think the PCI device ID is the only option
I'm afraid.
One question that popped into my mind is: what happens if e.g. you have
both an E810 and an E825 present in the system? You cannot load two ice
drivers (one in-tree, another OOT) at the same time.
> Thanks,
>
> Chris
Side-note: Be aware that customer support folk do not usually monitor
this mailing list (myself being an exception rather than the rule). If
you want / need prompt updates and something you can share with your
team / manager for tracking, please open a support thread using the
established support processes (e.g. IPS [1]).
Best regards
Dawid
[1]
https://www.intel.com/content/www/us/en/support/articles/000057045/ethernet-products.html
prev parent reply other threads:[~2026-03-12 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 18:37 [Intel-wired-lan] is there a way other than PCI IDs to distinguish E810 from E825/E830? Chris Friesen via Intel-wired-lan
2026-03-12 16:17 ` Przemek Kitszel
2026-03-12 20:24 ` Dawid Osuchowski [this message]
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=de5cc621-7ff1-446f-9700-f342b0527fb0@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--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