Russell King wrote at Wednesday, February 29, 2012 1:45 PM:
...

So, really, comparing a standard uImage produced by the standard kernel
with gzipped Image is far from a fair comparison.  And that's actually
another argument for getting rid of the uImage target... it may make
people think a bit about what they're doing rather than accepting
whatever default location someone else chose for their kernel.

That seems like more of an argument for making the uImage target use
-T kernel_noload unconditionally, rather than removing the target.
Since doing so would solve the issue about the kernel picking a load
address.

That is, ignoring any arguments about breaking existing workflows at
least...

-- 
nvpublic