From: gnomes@lxorguk.ukuu.org.uk (One Thousand Gnomes)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: add Device Tree for the Armada 385 RD board
Date: Fri, 7 Mar 2014 21:42:32 +0000 [thread overview]
Message-ID: <20140307214232.795e76b8@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140306172339.GP4780@lunn.ch>
On Thu, 6 Mar 2014 18:23:39 +0100
Andrew Lunn <andrew@lunn.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
prev parent reply other threads:[~2014-03-07 21:42 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
2014-03-06 14:21 ` Andrew Lunn
2014-03-06 14:31 ` Gregory CLEMENT
2014-03-06 14:46 ` Andrew Lunn
2014-03-06 14:51 ` Gregory CLEMENT
2014-03-06 15:47 ` Gregory CLEMENT
2014-03-06 16:02 ` Ezequiel Garcia
2014-03-06 17:23 ` Andrew Lunn
2014-03-06 19:17 ` Ezequiel Garcia
2014-03-07 9:53 ` Gregory CLEMENT
2014-03-07 14:44 ` Jason Cooper
2014-03-07 21:42 ` One Thousand Gnomes [this message]
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=20140307214232.795e76b8@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).