Skip to content

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

Andrew Lunn linux-arm-kernel 1 version New

Get series with b4
b4 am [email protected]

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
Quoted 15 lines

Just to chime in a bit here.. We also hit this problem on Kirkwood, and fixed it in the bootloader. The power on default for Kirkwood chips is 0xd0000000 and Linux has long required the bootloader to move it.. Not sure why 370/XP dropped this.

Also, can you talk abit more about how this works to give more low DDR memory? The docs say you can't overlap windows, and DDR CS's have a power of two size/alignment requirement.

Does this mean the desire is to place a DDR CS from 3G -> 3.5G?

Quoted 3 lines

For example, I'm currently booting alternatively with an old and a new bootloader (to test that things work properly), and in both cases I'm booting old style, DTB-appended, with ATAGs.

Quoted 5 lines

IMHO the DTB must match both the hardware *and* the bootloader. The bootloader is setting the address map, the DTB contains that address map, they must all match together.

Using a DTB property really is the right way to go.

Interesting you said that, yet for your kirkwood, you hacked your bootloader rather than Linux.

I think in practice, it is not going to be easy to match the DTB to the hardware and the bootloader. Look at debians flash-kernel, used to prepare the kernel for an embedded system. For each target it has a database entry:

Machine: Globalscale Technologies Dreamplug
Kernel-Flavors: kirkwood
DTB-Id: kirkwood-dreamplug.dtb
DTB-Append: yes
U-Boot-Kernel-Address: 0x00008000
U-Boot-Initrd-Address: 0x0
Boot-Device: /dev/sda1
Boot-Kernel-Path: uImage
Boot-Initrd-Path: uInitrd
Boot-DTB-Path: dtb
Required-Packages: u-boot-tools
Bootloader-sets-root: no

So it appends the kirkwood-dreamplug.dtb blob to the kernel. What you are saying is that it also needs to somehow query the version of uboot running on the hardware so it can pick the correct dtb blob from a collection of kirkwood-dreamplug.dtb blobs and append it to the kernel.

Is it even possible to query the uboot version from Linux?

To keep the problems tractable, we should not really be dependent on the bootloader version.

Andrew