netdev - 2500base-x capable sfp copper module?

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: <20200702182120.6d11bf70@dellmb.labs.office.nic.cz>
Date:   Thu, 2 Jul 2020 18:21:20 +0200
From:   Marek Behún <marek.behun@....cz>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     netdev@...r.kernel.org
Subject: 2500base-x capable sfp copper module?

Hello Russell,

We are trying to find a copper SFP module capable of 2.5G speeds for
Turris Omnia (2500base-x is max for SERDES on Omnia).

We have tried MikroTik S+RJ10, which is a 10G capable copper SFP
module. But this module does not export access (via I2C) to its internal
PHY (which should be Marvell 88X3310).
Without access to the PHY it seems that the host side of the SFP is
configured at 10G and we are unable to change it to 2500base-x.

We have another module, Rollball RTSFP-10G, which contains the same
PHY, but this is visible on the I2C bus at address 0x56.
For some reason I am unable to access registers of the PHY via clause
45 protocol. The code in drivers/net/phy/mdio-i2c.c always returns
0xffff when reading via clause 45.
When accessing via clause 22, the registers are visible, but we are
unable to change to 2500base-x with these registers.

Do you think this is a problem of how the SFP module is
wired/programmed?

Do you know of 2500base-x capable copper SFP module which would work?
Maybe one based on the same Marvell PHY, but such that the clause 45
register access works?

Thank you.

Marek