[PATCH] ARM: mvebu: use 0xf1000000 as internal registers on Armada 370 DB

Andrew Lunn andrew at lunn.ch
Thu Apr 2 06:35:27 PDT 2015


On Thu, Apr 02, 2015 at 03:28:09PM +0200, Arnd Bergmann wrote:
> 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 at 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.

Hi Arnd

Changing to 0xf100000 is the revert. Kirkwood and Dove are at
0xf100000 and the regression was introduced with early Armada XP
boards and spread to 370.

       Andrew



More information about the linux-arm-kernel mailing list