netdev - Re: Checking for MDIO phy address 0

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]

Date:   Mon, 28 Nov 2016 22:17:46 +0000
From:   "Phil Endecott" <spam_from_netdev@...zphil.org>
To:     "Florian Fainelli" <f.fainelli@...il.com>
Cc:     <netdev@...r.kernel.org>
Subject: Re: Checking for MDIO phy address 0

Hi Florian,

Florian Fainelli wrote:
> On 11/28/2016 10:53 AM, Phil Endecott wrote:

>> Anyway, my reason for this message is to suggest a runtime diagnostic 
>> message somewhere if address 0 is used - this could have saved me a lot of 
>> work! If someone can suggest the right place to add this I can prepare a 
>> patch.
>
> Address 0 can be made special or not, but there is no programmatic way
> to tell without scanning the MDIO bus for devices, so I don't think a
> warning is going to help at all to warn about that. There are also tons
> of cases where the address is just treated like any other address, which
> is typical with MDIO connected Ethernet switches where PHY@0 is just the
> switch's port 0 built-in PHY for instance.

Thanks for the quick reply; I'll forget that idea.

Regarding the actual problem with the 0 address on this board, I
have been told that someone at APM is going to look into it.  Fingers
crossed that it's fixable somewhere in a driver.  I'll update the list
if necessary.


Cheers,  Phil.