Dear Simon Glass,
In message CAPnjgZ1vb9DB=UkrS0tG47zrYubc0SvG5vK0whUvN3b7_5uU5Q@mail.gmail.com you wrote:
copy it." Given the way Linux zImage works, I know this works fine on all those SoCs, and even if it didn't, the U-Boot scripts for those SoCs could arrange for the uImage to be loaded to a SoC-specific address that the zImage /would/ work at.
Fair enough so far as it goes.
But why should U-Boot need to be configured with image-specific information, when we have well defined ways to store exactly that needed information in the image itself? That would be a full step backward.
But doesn't that mean that we are stuck with zImage and cannot have U-Boot do the decompression?
Indeed - this is just one of the disadvatages and reasons why I reject that new code.
If I find some time I will eventually re-review the IH_TYPE_*_REL patches, and most probably apply them.
Best regards,
Wolfgang Denk