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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 21 Apr 2022 15:30:38 +0200 From: Andrew Lunn <andrew@...n.ch> To: "Russell King (Oracle)" <linux@...linux.org.uk> Cc: Josua Mayer <josua@...id-run.com>, netdev@...r.kernel.org, alvaro.karsz@...id-run.com, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>, NXP Linux Team <linux-imx@....com> Subject: Re: [PATCH v2 3/3] ARM: dts: imx6qdl-sr-som: update phy configuration for som revision 1.9 > The only other ways around this that I can see would be to have some > way to flag in DT that the PHYs are "optional" - if they're not found > while probing the hardware, then don't whinge about them. Or have > u-boot discover which address the PHY is located, and update the DT > blob passed to the kernel to disable the PHY addresses that aren't > present. Or edit the DT to update the node name and reg property. Or > something along those lines. uboot sounds like the best option. I don't know if we currently support the status property for PHYs. Maybe the .dtsi file should have them all status = "disabled"; and uboot can flip the populated ones to "okay". Or maybe the other way around to handle older bootloaders. Andrew
Powered by blists - more mailing lists