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] [day] [month] [year] [list]
Message-ID: <CAK+owojR_pRpZKJcyd-QgOBNCQo2XiVs7J7GWzEH98T_poWANw@mail.gmail.com>
Date: Thu, 15 May 2025 09:02:02 +0200
From: Stefano Radaelli <stefano.radaelli21@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, linux-kernel@...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>, Xu Liang <lxu@...linear.com>
Subject: Re: [PATCH v2] net: phy: mxl-8611: add support for MaxLinear
 MxL86110/MxL86111 PHY

Hi Andrew,

Yes, I can confirm that the MXL86110 only supports copper (10/100/1000BASE-T)
over RGMII, and does not include any dual media or fiber logic.
That definitely simplifies things.

I'll go ahead and work on a revised version of the driver that supports only
the MXL86110 for now, addressing the issues you pointed out. The MXL86111
support can then be reworked and submitted separately once it's
cleaned up properly.

I’ll start a new thread with the updated patchset for the MXL86110
driver once it's ready.

Thanks again for your patience,
Stefano

Il giorno gio 15 mag 2025 alle ore 01:56 Andrew Lunn <andrew@...n.ch>
ha scritto:
>
> On Thu, May 15, 2025 at 12:29:48AM +0200, Stefano Radaelli wrote:
> > Hi Andrew,
> >
> > Thanks again for your detailed review and suggestions,
> > I really appreciate the time you took to go through the patch.
> >
> > After reviewing your feedback, I realized that most of the more complex issues
> > are specific to the MXL86111. The MXL86110 side, on the other hand, seems much
> > closer to being ready once I address the points you raised.
>
> I did not look too close. Does the MXL86110 not have this dual
> Copper/Fibre setup? Removing that will make the driver a lot
> simpler. So yes, submitting a simpler, more restricted driver is fine.
>
>         Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ