devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	Tawfik Bayouk <tawfik@marvell.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nadav Haklai <nadavh@marvell.com>,
	Lior Amsalem <alior@marvell.com>,
	linux-arm-kernel@lists.infradead.org,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] ARM: mvebu: add Device Tree for the Armada 385 RD board
Date: Thu, 6 Mar 2014 18:23:39 +0100	[thread overview]
Message-ID: <20140306172339.GP4780@lunn.ch> (raw)
In-Reply-To: <20140306160213.GA4327@arch.cereza>

> 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.

   Andrew

  reply	other threads:[~2014-03-06 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 12:11 [PATCH] ARM: mvebu: add Device Tree for the Armada 385 RD board Gregory CLEMENT
2014-03-06 13:14 ` Andrew Lunn
2014-03-06 13:26   ` Gregory CLEMENT
     [not found]     ` <5318779C.8030901-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-03-06 14:21       ` Andrew Lunn
2014-03-06 14:31         ` Gregory CLEMENT
     [not found]           ` <531886B4.2070002-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-03-06 14:46             ` Andrew Lunn
     [not found]               ` <20140306144600.GM4780-g2DYL2Zd6BY@public.gmane.org>
2014-03-06 14:51                 ` Gregory CLEMENT
     [not found]                   ` <53188B73.4000109-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-03-06 15:47                     ` Gregory CLEMENT
2014-03-06 16:02                       ` Ezequiel Garcia
2014-03-06 17:23                         ` Andrew Lunn [this message]
2014-03-06 19:17                           ` Ezequiel Garcia
     [not found]                             ` <20140306191747.GA32655-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>
2014-03-07  9:53                               ` Gregory CLEMENT
2014-03-07 14:44                                 ` Jason Cooper
2014-03-07 21:42                           ` One Thousand Gnomes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140306172339.GP4780@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alior@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nadavh@marvell.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).