Hei hei,

On Tue, Nov 29, 2016 at 10:04:19AM +0100, Marc Kleine-Budde wrote:
> What happens if you build a older kernel and don't configure
> PTXCONF_KERNEL_LOADADDR via ptxdist? Does it break while it used to work
> with an older ptxdist?

If I understood you correctly, that's not the case. Older kernels
don't need this passed, but somehow determine it. For example with
ptxdist 2015.10 and kernel 2.6.36.4 for at91sam9g20ek the loadaddr in
the final uImage is 0x20008000. The code for generating the image is
in arch/arm/boot/Makefile but I could not find out, where the actual
address comes from, if I don't pass LOADADDR. If I pass it (e.g. with
the backported patch) the address I pass is used (tried this with
another address).

So while LOADADDR needs to be passed for newer kernels, the build is
successful on older kernels with or without passing LOADADDR. Without
it is somehow determined by the kernel make files I suppose. When
passing LOADADDR the result is the same as for newer kernels.

Does this answer your question?

Í'm not sure how the patch would have to be extended, though.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***