Re: [U-Boot] [PATCH v2 1/3] image: Make image_get_fdt work like image_get_{ram_disk, kernel}

Dear Marek Vasut,

In message 201111052039.34646.marek.vasut@gmail.com you wrote:

...

Just a quick Q. What is the ultimate intent here? Should we be aiming to have U-Boot copy and decompress the data into RAM ready for Linux?

Nope, not at all. We have a problem with booting linux images which support multiple different SoCs (because the RAM might be elsewhere for different SoCs).

You are wrong. The agreement was to allow for addresses (load address, entry point address) that are relative to the start of system RAM.

That's not the point. We need to load FDT, load zImage, setup the regs and boot it from where we load the zImage. The uImage envelope contains fixed address to where the kernel image is loaded, which interferes with kernel's runtime patching of the kernel base address (zreladdr).

You ignore the discussions and proposals that were made.

uImage blocks this because it forces u-boot to copy zImage to fixed address.

Nonsense.

Best regards,

Wolfgang Denk