public inbox for intel-wired-lan@osuosl.org
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Chris Friesen <chris.friesen@windriver.com>,
	Tony Nguyen <anthony.l.nguyen@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 17:17:18 +0100	[thread overview]
Message-ID: <9df36abb-705f-44bf-a609-76e3ff827c56@intel.com> (raw)
In-Reply-To: <04025549-91a4-47a8-b874-eaeb35a429bd@windriver.com>

On 3/9/26 19:37, Chris Friesen wrote:
> 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
> 

you are asking this question on the public mailing list about in-tree
drivers, here recommendation is to use in-tree driver, always

as "also OOT" developer, I would say it it sometime warranted to use
OOT, but then don't mix and either stick to all OOT or all upstream

  reply	other threads:[~2026-03-12 16:17 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 [this message]
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=9df36abb-705f-44bf-a609-76e3ff827c56@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=chris.friesen@windriver.com \
    --cc=intel-wired-lan@lists.osuosl.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