linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: use 0xf1000000 as internal registers on Armada 370 DB
Date: Thu, 02 Apr 2015 15:28:09 +0200	[thread overview]
Message-ID: <2321040.CmsL1gluUd@wuerfel> (raw)
In-Reply-To: <1427966184-8288-1-git-send-email-thomas.petazzoni@free-electrons.com>

On Thursday 02 April 2015 11:16:24 Thomas Petazzoni wrote:
> The Armada 370 DB boards are now being used with a more recent version
> of U-Boot, which has Device Tree support, and remaps internal
> registers at 0xf1000000 like most of the other Marvell EBU platforms.
> 
> Consequently, this commit updates the Device Tree describing this
> platform to use this new internal register address, so that the
> mainline kernel can easily be used on such boards that use a modern
> bootloader. A comment is also added to warn users who could have
> boards with an older bootloader version.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

I think it would be better to add a new .dts file that includes the
former, and give it a new name, such as armada-370-db-broken-uboot.dts.

We should not stop supporting the older versions, and it would be better
to revert the bootloader change in their u-boot before it spreads too far.

	Arnd

  reply	other threads:[~2015-04-02 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02  9:16 [PATCH] ARM: mvebu: use 0xf1000000 as internal registers on Armada 370 DB Thomas Petazzoni
2015-04-02 13:28 ` Arnd Bergmann [this message]
2015-04-02 13:35   ` Andrew Lunn
2015-04-02 13:36   ` Thomas Petazzoni
2015-04-02 14:09     ` Arnd Bergmann
2015-04-02 14:16       ` Thomas Petazzoni
2015-04-02 14:48         ` Russell King - ARM Linux
2015-04-02 15:02           ` Thomas Petazzoni
2015-04-02 15:25             ` Russell King - ARM Linux
2015-04-02 14:48         ` Jason Cooper
2015-04-02 15:35         ` Gregory CLEMENT
2015-04-02 15:33           ` Andrew Lunn
2015-04-03  7:49             ` 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=2321040.CmsL1gluUd@wuerfel \
    --to=arnd@arndb.de \
    --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).