linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] arm: preserve ATAGS in /chosen/atags in the Device Tree
Date: Fri, 7 Jun 2013 19:16:51 +0200	[thread overview]
Message-ID: <20130607191651.0baa1c7d@skate> (raw)
In-Reply-To: <20130607143249.GR23859@titan.lakedaemon.net>

Dear Jason Cooper,

On Fri, 7 Jun 2013 10:32:49 -0400, Jason Cooper wrote:

> > Well, I don't think what you say here is really fair. Before the DT was
> > in place, unless I missed it, there was no standard way of letting the
> > bootloader pass MAC addresses to the kernel. And Marvell's development
> > on those Armada 370/XP platforms predates the introduction of the
> > Device Tree in the Linux kernel (the code we have originally been give
> > was a 2.6.3x), so it's really not their fault to not have a DT-capable
> > bootloader at this point.
> 
> To be accurate, I think Nico is referring to the fact that Marvell
> assigned their own ATAG without going through Russell.

Right, that's true.

> However, just like mach-types, are we assigning any new atags?  Can we
> consider them deprecated?  If so, that changes the game.  Then what
> Thomas is proposing is a "legacy compatibility" patch, as opposed to a
> hole vendors can use to do their own thing.
> 
> We could add Arnd's suggestion of a time bomb on the common code in
> atags_to_fdt.c to prevent mis-use.
> 
> I'm not 100% convinced of this, and I actually tend to agree with Nico
> here, but I'd also like to find a workable solution.

I perfectly understand Nico and Russell concerns, for sure. But I'd
also like to find a workable solution:
 
 * Passing the MAC address on the kernel command line is not something
   that the network maintainer likes. See
   http://lists.openwall.net/netdev/2011/11/17/82 and Dave Miller's
   answer http://lists.openwall.net/netdev/2011/11/17/83.

 * Parsing the U-Boot environment is really not easy. How does the
   kernel know where this environment is located? What if another
   bootloader than U-Boot is used? Reading the U-Boot environment from
   the kernel sounds clunky.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-06-07 17:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  6:40 [PATCH 0/5] Mechanism for platform-specific parsing of ATAGs Thomas Petazzoni
2013-06-05  6:40 ` [PATCH 1/5] ARM: mvebu: set aliases for ethernet controllers Thomas Petazzoni
2013-06-05  6:40 ` [PATCH 2/5] arm: preserve ATAGS in /chosen/atags in the Device Tree Thomas Petazzoni
2013-06-05 13:27   ` Jason Cooper
2013-06-06 12:28   ` Thomas Petazzoni
2013-06-06 17:27     ` Nicolas Pitre
2013-06-07  9:21       ` Thomas Petazzoni
2013-06-07 14:32         ` Jason Cooper
2013-06-07 17:16           ` Thomas Petazzoni [this message]
2013-06-07 17:59             ` Jason Cooper
2013-06-08  4:50             ` Nicolas Pitre
2013-06-08 14:54               ` Jason Cooper
2013-06-08  7:59         ` Russell King - ARM Linux
2013-06-08 18:54         ` Rob Herring
2013-06-08 18:59           ` Russell King - ARM Linux
2013-06-05  6:40 ` [PATCH 3/5] of: net: introduce a of_set_mac_address() helper function Thomas Petazzoni
2013-06-05  7:13   ` Andrew Lunn
2013-06-05  7:18     ` Thomas Petazzoni
2013-06-05 11:58   ` Grant Likely
2013-06-05  6:40 ` [PATCH 4/5] arm: mxs: use the newly introduced of_set_mac_address() helper Thomas Petazzoni
2013-06-05  6:40 ` [PATCH 5/5] arm: mvebu: parse ATAGS to find the network interfaces MAC addresses Thomas Petazzoni

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=20130607191651.0baa1c7d@skate \
    --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).