[PATCH 4/5] ARM: mvebu: Allow multiple SoCs

Sebastian Hesselbarth sebastian.hesselbarth at gmail.com
Mon Sep 15 14:12:03 PDT 2014

On 09/15/2014 11:13 AM, Sascha Hauer wrote:
> On Mon, Sep 15, 2014 at 10:00:40AM +0200, Sebastian Hesselbarth wrote:
>> On 09/15/2014 09:41 AM, Sascha Hauer wrote:
>>> Now that the correct SoC specific memory fixup function is called
>>> we can allow to select multiple SoCs in Kconfig.
>>> Signed-off-by: Sascha Hauer <s.hauer at pengutronix.de>
>> Sascha,
>> thanks for the patches, I'll give them a try later. FWIW, this
>> patch allows to build Kirkwood together with Dove and Armada ones,
>> which will not work at all. Kirkwood is armv5, while the others
>> are armv7. There is no way you run a multiv7 barebox on kirkwood,
>> right?
> Oh, I didn't realize that Kirkwood is armv5. It should work though.
> The only reason to additionally add a mvebu_v7_config is to make
> Thumb2 mode available to the SoCs that support it.

I did some initial testing on Kirkwood Guruplug. In mvebu_defconfig
you select CONFIG_AEABI=y resulting in

$ readelf -h barebox | grep Flags
  Flags:                             0x5000000, Version5 EABI

And failing on Kirkwood at some places with

Board: Globalscale Technologies Guruplug Server Plus
SoC: Marvell 6281 rev 3
mdio_bus: miibus0: probed
unable to handle paging request at address 0x01f0ebac
pc : [<03e0de20>]    lr : [<03e0de08>]
sp : 03fffeb0  ip : 03fffea8  fp : 00000001
r10: 03ff4000  r9 : 01000e00  r8 : 01003a84
r7 : 01f07324  r6 : 03e55f88  r5 : 01f0eaa4  r4 : 01f0eaa8
r3 : 00000000  r2 : 00000040  r1 : 00000104  r0 : 01f11094
Flags: Nzcv  IRQs off  FIQs off  Mode SVC_32
[<03e0de20>] (mdio_bus_probe+0x150/0x188) from [<03e0cb24>]
[<03e0cb24>] (device_probe+0x1c/0x70) from [<03e0cbbc>]
[<03e0cbbc>] (match.part.2+0x44/0x50) from [<03e0cda8>]
[<03e0cda8>] (register_device+0x118/0x168) from [<03e0d2e8>]
[<03e0d2e8>] (phy_register_device+0x2c/0x94) from [<03e0df9c>]
[<03e0df9c>] (mdiobus_register+0x144/0x18c) from [<03e0ce8c>]
[<03e0ce8c>] (platform_probe+0x10/0x14) from [<03e0cb24>]
[<03e0cb24>] (device_probe+0x1c/0x70) from [<03e0cbbc>]
[<03e0cbbc>] (match.part.2+0x44/0x50) from [<03e0cc58>]
[<03e0cc58>] (register_driver+0x90/0xc8) from [<03e00ae8>]
[<03e00ae8>] (start_barebox+0x28/0x130) from [<03e3e3e8>]
[<03e3e3e8>] (__start+0xf8/0x10c) from [<03e00004>]

[<03e3dce0>] (unwind_backtrace+0x0/0xa0) from [<03e240a8>] (panic+0x28/0x48)
[<03e240a8>] (panic+0x28/0x48) from [<03e3e220>] (do_exception+0x10/0x14)
[<03e3e220>] (do_exception+0x10/0x14) from [<03e3e2ac>]
[<03e3e2ac>] (do_data_abort+0x2c/0x38) from [<03e3dee8>]

I first noticed that with orion-mdio disabled and on calling
devinfo. Looks like u64 dereferencing is definitely causing
this but I admit, I haven't looked at mdio.

Disabling CONFIG_AEABI gives

$ readelf -h barebox | grep Flags
  Flags:                             0x600, GNU EABI, software FP, VFP

which also works in a Multi-SoC image on Kirkwood.

>>>  #
> Instead of removing this I could turn this into
> comment "Kirkwood based boards"

I am not too much into v5/v7 differences (or EABI FWIW). If
you say, a multi_v5+v7 image is fine, I am too.

I'll continue testing on !KIRKWOOD tomorrow evening.


More information about the barebox mailing list