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] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bbe2e1a-3ff0-4cf2-8d46-5f806f112925@lunn.ch>
Date: Wed, 16 Oct 2024 23:43:31 +0200
From: Andrew Lunn <andrew@...n.ch>
To: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: micrel ksz8081 RMII phy and clause-22 broadcast

> 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.

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.

	Andrew