netdev - Re: [support request]: where should I register this (apparently not supported yet) transceiver?

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <da8834aa-da77-4633-ac6f-d2b738a97337@lunn.ch>
Date: Thu, 12 Jun 2025 14:18:04 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Janpieter Sollie <janpieter.sollie@...elmail.de>
Cc: netdev@...r.kernel.org
Subject: Re: [support request]: where should I register this (apparently not
 supported yet) transceiver?

On Thu, Jun 12, 2025 at 10:58:23AM +0200, Janpieter Sollie wrote:
> Hi Everyone,
> 
> I'm looking for support to register my trainsceiver in the phy subsystem.
> This RJ45 transceiver (ZK-10G-TX) looks very weird in ethtool:
> 
> |> Identifier : 0x03 (SFP)
> > Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
> > Connector : 0x07 (LC)
> > Transceiver codes : 0x10 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> > Transceiver type : 10G Ethernet: 10G Base-SR
> > Encoding : 0x06 (64B/66B) BR
> > Nominal : 10300MBd
> > Rate identifier : 0x00 (unspecified)
> > Length (SMF) : 0km
> > Length (OM2) : 80m
> > Length (OM1) : 20m
> > Length (Copper or Active cable) : 0m
> > Length (OM3) : 300m Laser
> > wavelength : 850nm
> > Vendor name : OEM
> > Vendor OUI : 00:1b:21
> > Vendor PN : ZK-10G-TX
> > Vendor rev : 1
> > Option values : 0x00 0x1a
> > Option : TX_DISABLE implemented
> > BR margin max : 0%
> > BR margin min : 0%
> > Vendor SN : 2505010443
> > Date code : 250412
> > Optical diagnostics support : Yes
> > Laser bias current : 6.000 mA
> > Laser output power : 0.5000 mW / -3.01 dBm
> > Receiver signal average optical power : 0.4000 mW / -3.98 dBm
> ...
> 
> I cannot read its pages with i2c tools.
> It has a big "AQR113C" sticker on it,

The protocol to talk to the PHY is not defined in the standards.
However, there are two main protocols. It could be this PHY needs
rollball.

Please try adding an entry to drivers/net/phy/sfp.c:sfp_quirk[]
for this SFP, using sfp_fixup_rollball.

It might work, it might not...

	Andrew