netdev - Re: [PATCH net-next 01/15] net: phy: aquantia: rename AQR412 to AQR412C and add real AQR412

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: <162ae90f-d233-4415-ba98-d4292be41c21@lunn.ch>
Date: Thu, 21 Aug 2025 17:35:43 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Daniel Golle <daniel@...rotopia.org>, linux-kernel@...r.kernel.org,
	Nikita Yushchenko <nikita.yoush@...entembedded.com>,
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Robert Marko <robimarko@...il.com>,
	Paweł Owoc <frut3k7@...il.com>,
	Sean Anderson <sean.anderson@...o.com>,
	Jon Hunter <jonathanh@...dia.com>
Subject: Re: [PATCH net-next 01/15] net: phy: aquantia: rename AQR412 to
 AQR412C and add real AQR412

On Thu, Aug 21, 2025 at 06:20:08PM +0300, Vladimir Oltean wrote:
> I have noticed from schematics and firmware images that the PHY for
> which I've previously added support in commit 973fbe68df39 ("net: phy:
> aquantia: add AQR112 and AQR412 PHY IDs") is actually an AQR412C, not
> AQR412.
> 
> These are actually PHYs from the same generation, and Marvell documents
> them as differing only in the size of the FCCSP package: 19x19 mm for
> the AQR412, vs 14x12mm for the Compact AQR412C.
> 
> I don't think there is any point in backporting this to stable kernels,
> since the PHYs are identical in capabilities, and no functional
> difference is expected regardless of how the PHY is identified.
> 
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>

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

    Andrew