From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: mvebu: adjust ethernet aliases according to U-Boot requirements for A38x
Date: Thu, 13 Nov 2014 16:02:01 +0100 [thread overview]
Message-ID: <20141113160201.2c426ba2@free-electrons.com> (raw)
In-Reply-To: <CAPv3WKdjaMF--GQTF42Zk=kYOYpyvBONrOALG3nnhh25a0_72w@mail.gmail.com>
Dear Marcin Wojtas,
On Thu, 13 Nov 2014 15:55:31 +0100, Marcin Wojtas wrote:
> 2014-11-13 9:14 GMT+01:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
> > Dear Marcin Wojtas,
> >
> > On Thu, 13 Nov 2014 00:39:59 +0100, Marcin Wojtas wrote:
> >> The vendor bootloader provided for Armada 38x boards expects an
> >> alias for the ethernet nodes, which is used to fixup the MAC address.
> >> The alias format naming is strict.
> >
> > I believe this needs a bit more explanation: why would we care about
> > the "vendor bootloader" ? What are expecting the mainline versions of
> > popular bootloaders like U-Boot and Barebox ? What are other platforms
> > supported in the mainline doing ?
>
> In order to update MAC address entry in Device Tree both mainline U-Boot
> (in function fdt_fixup_ethernet) and Barebox (in function eth_of_fixup)
> accept same (and the only one) format of eth aliases, which is 'ethernetX',
> where X stands for interface number.
Yes, I know this, I had a look when I saw your patch.
> Other platforms in the mainline Linux, that comprise ethernet references in
> '/aliases' node (like various flavours of imx or sunXi), follow the naming
> scheme described above.
> Is this explanation sufficient? Do you think I should extend the commit log?
Yes, that's what I meant: in the commit log, taking as a justification
for the change a "vendor bootloader" is probably the worst possible
justification. Taking the mainline version of bootloaders and other
platforms supported in the kernel is a much stronger justification for
the change you're proposing.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-11-13 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1415835600-97188-1-git-send-email-mw@semihalf.com>
2014-11-13 8:02 ` [PATCH 0/5] Minor fixes for Marvell Armada 38x SoC Thomas Petazzoni
2014-11-13 15:28 ` Andrew Lunn
[not found] ` <1415835600-97188-2-git-send-email-mw@semihalf.com>
2014-11-13 8:03 ` [PATCH 1/5] ARM: mvebu: re-enable SDHCI driver for Armada 38x SoC in v7 defconfig Thomas Petazzoni
[not found] ` <1415835600-97188-3-git-send-email-mw@semihalf.com>
2014-11-13 8:07 ` [PATCH 2/5] ARM: mvebu: enable no-1-8-v flag for Armada 385 DB SDHCI interface Thomas Petazzoni
[not found] ` <1415835600-97188-6-git-send-email-mw@semihalf.com>
2014-11-13 8:12 ` [PATCH 5/5] ARM: mvebu: enable i2c device in mvebu_v7_defconfig Thomas Petazzoni
[not found] ` <1415835600-97188-5-git-send-email-mw@semihalf.com>
2014-11-13 8:14 ` [PATCH 4/5] ARM: mvebu: adjust ethernet aliases according to U-Boot requirements for A38x Thomas Petazzoni
2014-11-13 14:55 ` Marcin Wojtas
2014-11-13 15:02 ` Thomas Petazzoni [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=20141113160201.2c426ba2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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).