Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: add reference to ETH connectors for A385-AP
Date: Tue, 17 Nov 2015 16:21:18 +0000	[thread overview]
Message-ID: <20151117162118.GQ8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <7560280.yqEeu9J2fA@wuerfel>

On Tue, Nov 17, 2015 at 04:57:20PM +0100, Arnd Bergmann wrote:
> On Tuesday 17 November 2015 16:53:40 Thomas Petazzoni wrote:
> > This commit adds some comments to the Armada 385 AP Device Tree
> > description to indicate which Ethernet interface matches which
> > physical connector on the board.
> > 
> > This is especially useful on this board, since the mapping between the
> > logical interface names and the physical ports is not very
> > straightforward. It also doesn't match the numbering of the interfaces
> > done by U-Boot:
> > 
> >  U-Boot interface | Linux interface | Physical port
> >  -----------------+-----------------+--------------
> >    egiga0         |     eth2        |   CON4
> >    egiga1         |     eth0        |   CON2
> >    egiga2         |     eth1        |   CON3
> >  -----------------+-----------------+--------------
> > 
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> > 
> 
> Would it be possible to use entries in /aliases to fix the order of the
> interfaces and make them match the physical ports?

Unfortunately not, and I believe davem is averse to "fixing" this problem
in the kernel.  It's really problematical, especially if you are running
a debian based distro and want to be able to say "I want egiga0 configured
like _this_".  You're entirely at the mercy of the ordering that the DT
compiler decides to place the nodes, and the ordering which the kernel
decides to probe the interfaces, etc.

Yes, there's always the ethernet MAC which can be used to identify them,
but debian at least doesn't have a way to identify interfaces in its
/etc/network/interfaces file by ethernet MAC.

So, use the modern network-manager daemon... umm no, not if you want to
use bridging or any of the other such facilities.

This whole area is really very annoying.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-11-17 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 15:53 [PATCH] ARM: mvebu: add reference to ETH connectors for A385-AP Thomas Petazzoni
2015-11-17 15:57 ` Arnd Bergmann
2015-11-17 16:21   ` Russell King - ARM Linux [this message]
2015-11-17 16:37     ` Marcin Wojtas
2015-11-23 18:17       ` Gregory CLEMENT

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=20151117162118.GQ8644@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.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