From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Konrad Knitter <konrad.knitter@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] ice: add E835 device IDs
Date: Mon, 19 May 2025 13:11:02 +0200 [thread overview]
Message-ID: <46e45673-66fa-4942-a733-fdcbc95b5ee1@linux.intel.com> (raw)
In-Reply-To: <8c8999a7-d586-4bc6-9912-b088d9c3049f@molgen.mpg.de>
On 2025-05-16 10:57 PM, Paul Menzel wrote:
> Am 14.05.25 um 12:46 schrieb Dawid Osuchowski:
>> E835 is an enhanced version of the E830.
>> It continues to use the same set of commands, registers and interfaces
>> as other devices in the 800 Series.
>>
>> Following device IDs are added:
>> - 0x1248: Intel(R) Ethernet Controller E835-CC for backplane
>> - 0x1249: Intel(R) Ethernet Controller E835-CC for QSFP
>> - 0x124A: Intel(R) Ethernet Controller E835-CC for SFP
>> - 0x1261: Intel(R) Ethernet Controller E835-C for backplane
>> - 0x1262: Intel(R) Ethernet Controller E835-C for QSFP
>> - 0x1263: Intel(R) Ethernet Controller E835-C for SFP
>> - 0x1265: Intel(R) Ethernet Controller E835-L for backplane
>> - 0x1266: Intel(R) Ethernet Controller E835-L for QSFP
>> - 0x1267: Intel(R) Ethernet Controller E835-L for SFP
>
> Should you resend, it’d be great, if you added the datasheet name, where
> these id’s are present.
Sorry it isn't publicly available yet.
Best regards,
Dawid
> Kind regards,
>
> Paul
next prev parent reply other threads:[~2025-05-19 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 10:46 [PATCH iwl-next] ice: add E835 device IDs Dawid Osuchowski
2025-05-15 20:02 ` Simon Horman
2025-05-16 17:30 ` [Intel-wired-lan] " Tony Nguyen
2025-05-19 11:08 ` Dawid Osuchowski
2025-05-16 20:57 ` Paul Menzel
2025-05-19 11:11 ` Dawid Osuchowski [this message]
2025-05-22 7:01 ` Paul Menzel
2025-05-22 7:58 ` 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=46e45673-66fa-4942-a733-fdcbc95b5ee1@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=konrad.knitter@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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).