linux-kernel - Re: [PATCH] net: phy: bcm54811: add support for BroadR-Reach mode

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]

Date: Tue, 16 Apr 2024 16:10:07 +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, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: phy: bcm54811: add support for BroadR-Reach mode

> @@ -258,6 +257,9 @@ static const struct phy_setting settings[] = {
>  	PHY_SETTING(    100, HALF,    100baseT_Half		),
>  	PHY_SETTING(    100, HALF,    100baseFX_Half		),
>  	PHY_SETTING(    100, FULL,    100baseFX_Full		),
> +	PHY_SETTING(    100, FULL,    4BR100			),
> +	PHY_SETTING(    100, FULL,    2BR100			),
> +	PHY_SETTING(    100, FULL,    1BR100			),

Please could you explain the name convention. IEEE puts the speed
first, then some letters to indicate the media type, and then a number
for the number of pairs. Why is this not followed here? 100BaseBR4?
100BaseBR2? 100BaseBR1? Are these names part of the BroadR-Reach
standard?

Also, is there any compatibility? Are 100BaseT1 and 1BR100 compatible?

      Andrew