[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53199726.4080300@free-electrons.com>
Date: Fri, 07 Mar 2014 10:53:42 +0100
From: Gregory CLEMENT <gregory.clement@...e-electrons.com>
To: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
Andrew Lunn <andrew@...n.ch>
CC: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
devicetree@...r.kernel.org, Jason Cooper <jason@...edaemon.net>,
Tawfik Bayouk <tawfik@...vell.com>,
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 06/03/2014 20:17, Ezequiel Garcia wrote:
> On Mar 06, Andrew Lunn 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.
>>
I was aware of this solution, and indeed for the end user it is the thing
to do.
However my concern was more about the people testing the kernel early or for
people bringing up a new board. I fear that we will have many false bug report
about it.
For the second category, I think we should at least point this in the dtsi.
Thanks,
Gregory
>
> Right, makes perfect sense!
>
> So we can just keep the nodes address-ordered, without caring about the name?
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
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