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 20:14:44 +0200 [thread overview]
Message-ID: <20160824201444.487022de@free-electrons.com> (raw)
In-Reply-To: <20160824180727.GE14311@csclub.uwaterloo.ca>
Hello,
On Wed, 24 Aug 2016 14:07:27 -0400, Lennart Sorensen wrote:
> > The nice thing about having the order in the dtb I thought was that it
> > wont ever change.
>
> I wonder, if someone was to build a box with this cpu, and add a PCIe
> network device, which order would they get probed in? Any chance the
> PCIe could grab eth0 before the mvneta devices get probed?
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.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-24 18:16 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 [this message]
2016-08-24 18:27 ` Lennart Sorensen
2016-08-24 19:52 ` Thomas Petazzoni
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=20160824201444.487022de@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.