netdev - Re: [PATCH v12 4/4] net: phy: bcm-phy-lib: Implement BroadR-Reach link modes

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: <40ffc36c-0fc7-4195-ae3d-52750aa54eac@lunn.ch>
Date: Sat, 13 Jul 2024 20:30:01 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Kamil Horák (2N) <kamilh@...s.com>
Cc: florian.fainelli@...adcom.com, bcm-kernel-feedback-list@...adcom.com,
	hkallweit1@...il.com, linux@...linux.org.uk, davem@...emloft.net,
	edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
	robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
	f.fainelli@...il.com, kory.maincent@...tlin.com,
	netdev@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v12 4/4] net: phy: bcm-phy-lib: Implement BroadR-Reach
 link modes

On Fri, Jul 12, 2024 at 05:07:09PM +0200, Kamil Horák (2N) wrote:
> Implement single-pair BroadR-Reach modes on bcm5481x PHY by Broadcom.
> Create set of functions alternative to IEEE 802.3 to handle
> configuration of these modes on compatible Broadcom PHYs.
> There is only subset of capabilities supported because of limited
> collection of hardware available for the development.
> For BroadR-Reach capable PHYs, the LRE (Long Reach Ethernet)
> alternative register set is handled. Only bcm54811 PHY is verified,
> for bcm54810, there is some support possible but untested. There
> is no auto-negotiation of the link parameters (called LDS in the
> Broadcom terminology, Long-Distance Signaling) for bcm54811.
> It should be possible to enable LDS for bcm54810.
> 
> Signed-off-by: Kamil Horák (2N) <kamilh@...s.com>

Reviewed-by: Andrew Lunn <andrew@...n.ch>

    Andrew