Skip to content

Switch internal registers address to 0xF1 on Armada 370/XP

Thomas Petazzoni linux-arm-kernel 1 version New

Get series with b4
b4 am 20130522180842.7edcc3ee@skate

Versions newest first

  1. v1 Latest0 of 9 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 9 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/9] Switch internal registers address to 0xF1 on Armada 370/XP

Dear Willy Tarreau,

Quoted 7 lines · Willy Tarreau
Quoted 3 lines · Thomas Petazzoni

Yes, they could upgrade. But as of today, such upgrades do not even exist for the Mirabox and OpenBlocks AX3 boards. So what do we tell to those users?

I was assuming these boot loaders do already exist if they're shipping on some devices, but maybe not all yet.

The new bootloaders have started being offered by Marvell to board/system manufacturers since only a few weeks or so, so besides evaluation boards, there are not yet public products that use the new bootloaders. But the vast majority of Armada 370 and Armada XP platforms are still to be coming, and this vast majority will be using the new bootloader.

Quoted 9 lines
Quoted 4 lines

Of course, one option is simply to have a kconfig option "I am booting from an old bootloader", but with the CP15 trick, we've tried to make this automatic so that users don't have to understand the kind of gory details we are discussing right now.

Same as for ATAGS right now which are not necessarily the most obvious setting for end users. Better keep the trick on by default if it's safe enough. In fact I'm mostly concerned about the risk that it later breaks for even newer boot loaders. But then we'll have more feedback to decide.

As I suggested earlier, we can print a warning when people boot from an old bootloader, and then down the road get rid of the trick. Or move it under a conditional compilation so that the minority of remaining users will have to enable this particular option. This will anyway be needed if we want to go multiplatform with Dove, for example.

Quoted 3 lines

OK, that was what I was wondering about. Sorry for having bothere you with my questions but at least not it's much clearer that CP15 probably is the only viable solution.

We've also gone through a lot of thinking about this problem, and we've considered various options, and we came down to the following two options:

* Assume we're booted with a bootloader that has done the remapping at 0xf1. Works for all new platforms, breaks all the older platforms, unless people upgrade their bootloaders.

* Have a nicer way to handle the transition, and in this case, when you take into account all the complexities, the CP15 turned out to be the only really viable solution.

Best regards,

Thomas

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