lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1e7b314d-55d4-4e9b-9046-0dd624a5e347@linux.intel.com>
Date: Thu, 22 May 2025 09:58:21 +0200
From: Dawid Osuchowski <dawid.osuchowski@...ux.intel.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
 Konrad Knitter <konrad.knitter@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] ice: add E835 device IDs

On 2025-05-22 9:01 AM, Paul Menzel wrote:
> Dear Dawid,
> 
> 
> Am 19.05.25 um 13:11 schrieb Dawid Osuchowski:
>> 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.
> 
> Too bad, but the name of the datasheet would still be useful in the 
> commit message, so people could point to it, or, should it ever be made 
> public, can find it.

I understand your concern.

Given our datasheet naming scheme so far [1], I think folks
interested in viewing the datasheet can easily search our Resource & 
Documentation Center [2] to find what they're looking for once it 
becomes available.

[1] 
https://www.intel.com/content/www/us/en/content-details/613875/intel-ethernet-controller-e810-datasheet.html
[2] 
https://www.intel.com/content/www/us/en/resources-documentation/developer.html

Best regards,
Dawid

> 
> 
> Kind regards,
> 
> Paul


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ