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
| ||
|
Date: Sun, 22 Jan 2017 17:57:04 +0100 From: Andrew Lunn <andrew@...n.ch> To: Martin Blumenstingl <martin.blumenstingl@...glemail.com> Cc: devicetree@...r.kernel.org, netdev@...r.kernel.org, davem@...emloft.net, f.fainelli@...il.com, mark.rutland@....com, robh+dt@...nel.org Subject: Re: [PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID On Sun, Jan 22, 2017 at 05:41:32PM +0100, Martin Blumenstingl wrote: > The old description basically read like "ethernet-phy-idAAAA.BBBB" can > be specified when you know the actual PHY ID. However, specifying this > has a side-effect: it forces Linux to bind to a certain PHY driver (the > one that matches the ID given in the compatible string), ignoring the ID > which is reported by the actual PHY. > Whenever a device is shipped with (multiple) different PHYs during it's > production lifetime then explicitly specifying > "ethernet-phy-idAAAA.BBBB" could break certain revisions of that device. > > Signed-off-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com> Reviewed-by: Andrew Lunn <andrew@...n.ch> Thanks Andrew
Powered by blists - more mailing lists