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

Message-ID: <11c8694a-382c-4085-9e83-0a4fa4a362cb@lunn.ch>
Date: Fri, 13 Jun 2025 15:39:50 +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?

> Unfortunately, the result was not as I'd expect (on kernel 6.12.32):
> 
> > ... (booting kernel 6.12.32 with quirk) ...
> > [   37.832050] mtk_soc_eth 15100000.ethernet sfp-lan:
> validation with support 00,00000000,00000000,00000000 failed: -EINVAL
> > [   37.843056] sfp sfp2: sfp_add_phy failed: -EINVAL

So it probably cannot find the PHY.

> > ...
> 
> I tried the eepromfix of i2csfp:

Did you play with:

i2csfp I2CBUS rollball read|write DEVAD REGISTER [VALUE]

Try reading devad = 1, register = 2 and 3.

	Andrew