netdev - Re: net: macb: fail when there's no PHY

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: <rq90ks$mjq$1@ciao.gmane.io>
Date:   Wed, 2 Dec 2020 21:23:40 -0000 (UTC)
From:   Grant Edwards <grant.b.edwards@...il.com>
To:     netdev@...r.kernel.org
Subject: Re: net: macb: fail when there's no PHY

On 2020-12-02, Andrew Lunn <andrew@...n.ch> wrote:
>> > So it will access the MDIO bus of the PHY that is attached to the
>> > MAC.
>> 
>> If that's the case, wouldn't the ioctl() calls "just work" even when
>> only the fixed-phy mdio bus and fake PHY are declared in the device
>> tree?
>
> The fixed-link PHY is connected to the MAC. So the IOCTL calls will be
> made to the fixed-link fake MDIO bus.

So how do you control which of the two mdio buses is connected to
the MAC?

> There are plenty of examples to follow.

That's true, but knowing which ones do what you're trying to do is the
hard part. If you already know how to do it, it's easy to find
examples showing it.  :)

--
Grant