Switch internal registers address to 0xF1 on Armada 370/XP
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 of 9 patches 0 repliesNew
3 of 9 patches are in this archive. The cover letter announces 9.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 9/9 | arm: mvebu: switch internal register address at runtime if needed | +0 | 2 replies | |
| 9/9 | arm: mvebu: switch internal register address at runtime if needed | +0 | 1 reply | |
| 9/9 | arm: mvebu: switch internal register address at runtime if needed | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/9] Switch internal registers address to 0xF1 on Armada 370/XP
Quoted 6 lines
Quoted 3 lines
I don't see how this can fix the problem. Which internal register base address do we put in our Device Tree source in
arch/arm/boot/dts? The old one? The new one?The one matching the boot loader for that board, i.e. the new address for all boards but Mirabox and OpenBlocks.
Hi Thomas
Maybe i'm missunderstand Arnd, but i think he is suggesting a property somewhere in DT which says where the bootloader left the register space before jumping to the kernel. You can then look at this property and then decide if you need to remap or not. Only this one property needs to differ between old and new bootloader. You could even say, if the property is not in DT, a remap is needed.
However, i don't know if this can actually work. How early can you parse the DT in order to know where the serial port is for earlyprintk()? It also gets messy keeping track of the two different DT binary blobs and somehow having the probe the uboot version in order to install the right one. I don't know how i would include this into the debian flash-kernel for example.
I prefer the CP15 bit.
Andrew