[U-Boot] [PATCH v2 3/3] image: Allow images to indicate they're loadable at any address

Wolfgang Denk
2011-11-07T20:26:33Z

Dear Stephen Warren,

In message <74CDBE0F657A3D45AFBB94109FB122FF173F9A5035@HQMAIL01.nvidia.com> you wrote:
>
> > Your own IH_TYPE_*_REL patches are queued and will be merged soon.
>
> Oh. I kept pushing and pushing on these and kept meeting resistance. I

There was no resistance ever. There were just the normal review
comments.

> had absolutely no idea at all that there was agreement over those patches;
> the reviews just stopped happening after you refused to look at them

If there are no further complaints that usually menas the stuff is
sitting in the queue waiting to be processed. Sorry, but my bandwidth
_is_ limited.

> Anyway, I have withdrawn my support for those patches; please don't apply
> them. In my opinion, this new solution is far superior because:

Argh... So we are back at square one.

The problem with this new approach is that Linux kernel images are NOT
freely relocatable. They do have a fix entry point, even if this is
not an absolute address, but a relative one. The natural way to
handle this is exactly that: add support for images with relative
)offset based) load and entry point addresses.

Your new approahc is indeed simpler - actually it is too simplistic,
as you cannot record load address / entry point information any more.
It may work when using the kernel wrapper - but what if you don't want
to do that?

> > I do not see the need for yet another implementation for the very same
> > thing, so NAK.

The NAK remains. The new code will not go in.

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A star captain's most solemn oath is that he will give his life, even
his entire crew, rather than violate the Prime Directive.
-- Kirk, "The Omega Glory", stardate unknown