ARMADA 370 - Kernel panic during boot

[Thomas Petazzoni]

Hello,

On Mon, 29 Sep 2014 13:25:03 +0200, post at twien.net wrote:

> 	soc {
> 		ranges = <MBUS_ID(0xf0, 0x01) 0 0xd0000000 0x100000

Are you really sure about the 0xd0000000 value here? Your earlyprintk
works using CONFIG_DEBUG_MVEBU_UART_ALTERNATE=y according to
your .config, which indicates that your internal registers are mapped at
0xf1000000 and not at 0xd0000000 as your Device Tree indicates.

Can you change this line to:

	ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000

And try again?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com