netdev - SFP: Copper module with different PHY address (Netgear AGM734)

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

Message-ID: <d57b4fcd-2fa6-bc92-0650-72530fbdc0a8@aboehler.at>
Date:   Wed, 26 Apr 2023 18:47:33 +0200
From:   Andreas Böhler <news@...ehler.at>
To:     netdev@...r.kernel.org
Subject: SFP: Copper module with different PHY address (Netgear AGM734)

Hi,

I have a bunch of Netgear AGM734 copper SFP modules that I would like to 
use with my switches. Upon insertion, a message "no PHY detected" pops up.

Upon further investigation I found out that the Marvell PHY in these 
modules is at 0x53 and not at the expected 0x56. A quick check with a 
changed SFP_PHY_ADDR works as expected.

Which is the best scenario to proceed?

1. Always probe SFP_PHY_ADDR and SFP_PHY_ADDR - 3

2. Create a fixup for this specific module to probe at a different 
address. However, I'm afraid this might break "compatible" modules.

3. Something else?

Thanks,

Regards,
Andreas