[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140307214232.795e76b8@alan.etchedpixels.co.uk>
Date: Fri, 7 Mar 2014 21:42:32 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Andrew Lunn <andrew@...n.ch>
Cc: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
Gregory CLEMENT <gregory.clement@...e-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Jason Cooper <jason@...edaemon.net>,
Tawfik Bayouk <tawfik@...vell.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Nadav Haklai <nadavh@...vell.com>,
Lior Amsalem <alior@...vell.com>,
linux-arm-kernel@...ts.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH] ARM: mvebu: add Device Tree for the Armada 385 RD board
On Thu, 6 Mar 2014 18:23:39 +0100
Andrew Lunn <andrew@...n.ch> wrote:
> > Can't we fix this so the probe order doesn't affect the name?
> >
> > Is that sane?
>
> You are not supposed to trust the device name, since probing can
> happen in parallel, on different buses. udev should have rules to name
> the interfaces based on the MAC address. On my Debian system i have:
>
> /etc/udev/rules.d/70-persistent-net.rules
>
> So what is important is that the MAC addresses are assigned correctly
> to the device. And DT does that based on MMIO address, so should be
> reliable, independent of probe order.
Remembering of course thats its valid to have one MAC address per system
not per network controller, so this does blow up in certain cases. You
can still use udev rules for most of those cases to identify off some
other property.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists