On 24 October 2012 20:16, Maarten ter Huurne <maarten@xxxxxxxxxxxxxx> wrote: > On Tuesday 23 October 2012 21:43:59 Antony Pavlov wrote: >> Add the Kbuild files for the JZ4750D architecture and adds JZ4750D support >> to the MIPS Kbuild files. > [snip] >> diff --git a/arch/mips/jz4750d/Platform b/arch/mips/jz4750d/Platform >> new file mode 100644 >> index 0000000..2e4e050 >> --- /dev/null >> +++ b/arch/mips/jz4750d/Platform >> @@ -0,0 +1,3 @@ >> +platform-$(CONFIG_MACH_JZ4750D) += jz4750d/ >> +cflags-$(CONFIG_MACH_JZ4750D) += >> -I$(srctree)/arch/mips/include/asm/mach-jz4750d >> +load-$(CONFIG_MACH_JZ4750D) += 0xffffffff80010000 > > What is the purpose of padding the load address to 64 bits? > > The reason I'm asking is that we encountered a bug with that when creating a > u-boot image on a 32-bit host machine: the mkimage tool will only parse the > first 8 hex digits and then inserts the wrong load address into the uImage. I have just copied jz4740/Platform. I don't use U-Boot, so I have never faced this problem. -- Best regards, Antony Pavlov
