Switch internal registers address to 0xF1 on Armada 370/XP
Get series with b4
b4 am [email protected]Versions newest first
- 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.
Cover letter [PATCH 0/9] Switch internal registers address to 0xF1 on Armada 370/XP
Le 24/05/2013 01:40, Russell King - ARM Linux a ?crit :
Quoted 14 lines · Thomas Petazzoni
Quoted 7 lines
Russell,
Quoted 3 lines · Russell King - ARM Linux
No, I'm not asking about the principle. I'm asking
_inthis particular problemcase_who provides the DT blob?Quoted 6 lines
Quoted 2 lines
So the person to answer that question is Thomas or someone who is using the boards concerned.
The DTB is built from
arch/arm/boot/dts/, together with the kernel image itself. As far as I'm aware of, there is for the moment no plan to "burn" the DTB on the board and therefore make the Device Tree really separated from the kernel.
Quoted 9 lines
Right, so we're still in the position where we aren't dealing with vendor provided DT blobs... this also means of course that the DT blob isn't going to get updated by the boot loader depending on where it decides to set the registers.
I suspect as far as the boot loaders on these boards go, the DT blob is "just another file" to be loaded into memory by the boot loader, and it is completely untouched by the boot loader.
Russell,
this is a little more complicated, the bootloader does touch the DT blob, for example it sets the MAC addresses of the network interfaces, I believe it also sets UART0 parameters. It does this silently if it founds entries it knows about in the DT blob.
I guess the good idea would have been to ask Marvell to also update an MBUS entry in the DT blob instead of doing the CP15 trick. This would not have solved the earlyprintk problem however.
I also guess this is not feasible anymore since it would imply to have 3 different bootloader possibilities and 2 already is a pain to deal with.
Does this raise any new idea to someone ?
Cheers,
PS: I also got Marvell's confirmation, there is no way to avoid CPU hang when accessing an unmapped memory address, this triggers an external abort exception which is not recoverable in kernel mode.