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
| ||
|
Message-ID: <20220809214518.i6od5zbkmup76feb@pali> Date: Tue, 9 Aug 2022 23:45:18 +0200 From: Pali Rohár <pali@...nel.org> To: Tim Harvey <tharvey@...eworks.com> Cc: Sean Anderson <sean.anderson@...o.com>, Michal Suchánek <msuchanek@...e.de>, Stephen Hemminger <stephen@...workplumber.org>, netdev <netdev@...r.kernel.org>, u-boot <u-boot@...ts.denx.de>, Device Tree Mailing List <devicetree@...r.kernel.org> Subject: Re: ethernet<n> dt aliases implications in U-Boot and Linux On Tuesday 09 August 2022 14:39:05 Tim Harvey wrote: > I've been wondering the same as well which made me wonder what the > history of the 'aliases' node is and why its not used in most cases in > Linux. I know for the SOC's I work with we've always defined aliases > for ethernet<n>, gpio<n>, serial<n>, spi<n>, i2c<n>, mmc<n> etc. Where > did this practice come from and why are we putting that in Linux dts > files it if it's not used by Linux? U-Boot can modify on-the-fly Linux's DTB file when booting Linux kernel. For example it can put permanent MAC address into ethernet nodes from U-Boot env. Similarly it can modify other DT nodes. So even when Linux itself does not use particular alias, it is used by the bootloader.
Powered by blists - more mailing lists