ethernet<n> dt aliases implications in U-Boot and Linux

[Francesco Dolcini]

On Tue, Aug 09, 2022 at 02:39:05PM -0700, Tim Harvey wrote:
> On Tue, Aug 9, 2022 at 2:31 PM Pali Rohár <pali at kernel.org> wrote:
> > On Tuesday 09 August 2022 16:48:23 Sean Anderson wrote:
> > > On 8/8/22 5:45 PM, Michal Suchánek wrote:
> > > > On Mon, Aug 08, 2022 at 02:38:35PM -0700, Stephen Hemminger wrote:
> > > >> On Mon, 8 Aug 2022 23:09:45 +0200
> > > >> Michal Suchánek <msuchanek at suse.de> wrote:
> > > >> > On Mon, Aug 08, 2022 at 03:57:55PM -0400, Sean Anderson wrote:
> > > >> > > On 8/8/22 3:18 PM, Tim Harvey wrote:
> > > >> > > > Greetings,
> > > >> > > >
> > > >> > > > I'm trying to understand if there is any implication of 'ethernet<n>'
> > > >> > > > aliases in Linux such as:
> > > >> > > >         aliases {
> > > >> > > >                 ethernet0 = &eqos;
> > > >> > > >                 ethernet1 = &fec;
> 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?

These aliases are used also to be sure that the MAC address assigned to
the network device is the same between Linux and U-Boot.

Francesco