From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Ralph Sennhauser <ralph.sennhauser@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces
Date: Wed, 24 Aug 2016 21:52:00 +0200 [thread overview]
Message-ID: <20160824215200.22de30d1@free-electrons.com> (raw)
In-Reply-To: <20160824182758.GF14311@csclub.uwaterloo.ca>
Hello,
On Wed, 24 Aug 2016 14:27:58 -0400, Lennart Sorensen wrote:
> On Wed, Aug 24, 2016 at 08:14:44PM +0200, Thomas Petazzoni wrote:
> > Depends on the network driver I believe. But with an e1000e NIC plugged
> > in a PCIe slot, it indeed gets assigned as eth0, and the internal
> > mvneta devices get eth1, eth2, etc.
>
> Which of course means the change does not actually ensure the port
> ordering matches the marvell documentation or u-boot. It only handles
> the relative order of the ports. For now.
Correct.
> So since it doesn't actually work, maybe reverting it so it no longer
> violates the dtb ordeting rule makes sense.
I'll let the platform maintainers decide what's the least
intrusive/problematic option. Both solutions have drawbacks, so it's
really a "political" decision to make here.
> Doesn't mean openwrt/lede/etc don't have to deal with the ordering in
> the future if async probing takes off.
Not only async probing, but also PCIe devices, as you mentioned
earlier :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-24 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 13:11 [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces Ralph Sennhauser
2016-08-24 14:50 ` Thomas Petazzoni
2016-08-24 16:19 ` Lennart Sorensen
2016-08-24 16:43 ` Thomas Petazzoni
2016-08-24 17:10 ` Lennart Sorensen
2016-08-24 18:38 ` Lennart Sorensen
2016-08-24 17:10 ` Ralph Sennhauser
2016-08-24 18:07 ` Lennart Sorensen
2016-08-24 18:14 ` Thomas Petazzoni
2016-08-24 18:27 ` Lennart Sorensen
2016-08-24 19:52 ` Thomas Petazzoni [this message]
2016-08-24 20:51 ` Lennart Sorensen
2016-08-24 18:15 ` Thomas Petazzoni
2016-08-24 20:41 ` Ralph Sennhauser
2016-08-24 21:48 ` Jason Cooper
2016-08-25 7:38 ` Ralph Sennhauser
2016-08-25 19:40 ` Lennart Sorensen
2016-08-26 8:43 ` Gregory CLEMENT
2016-08-26 10:39 ` Ralph Sennhauser
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=20160824215200.22de30d1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=ralph.sennhauser@gmail.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