netdev - Re: micrel ksz8081 RMII phy and clause-22 broadcast

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: <20241017-skirmish-various-4e334907784c@thorsis.com>
Date: Thu, 17 Oct 2024 08:29:17 +0200
From: Alexander Dahl <ada@...rsis.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: micrel ksz8081 RMII phy and clause-22 broadcast

Hello Andrew,

Am Wed, Oct 16, 2024 at 11:43:31PM +0200 schrieb Andrew Lunn:
> > Would be happy if anyone could suggest a path forward here?
> 
> The hardware is different, so have a different dts file. You can then
> list the PHY at is real address, which will stop the phantom broadcast
> address PHY being created, and use a phy-handle to point to the real
> PHYs, so when the phantom broadcast PHY is disabled, it does not
> matter.

Yes, I think separate dts is a clean solution, creating those files is
no problem.  I just wanted to avoid the additional work for
integrating this into build, bootstrapping scripts, firmware upgrade
etc.  O:-)

Thanks for confirming, seriously appreciated. :-)

> I would say that listing multiple PHYS is just an opportunistic hack,
> which might work for simple cases, but soon leads to difficulties as
> the situation gets complex.

Right.  Thank you for taking the time to read.

Greets
Alex