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

Wolfgang Denk
2011-11-08T08:38:40Z

Dear Nicolas Pitre,

In message <alpine.LFD.2.02.1111071942150.3307@xanadu.home> you wrote:
>
> > But as you said yourself, the (raw) kernel is not relocatable. It
> > gets loaded and started at pre-defined (at image build time)
> > addresses. Only the kernel wrapper adds the complexity you are
> > complaining about. Drop it, then.
>
> Many of us insist on preserving that complexity. From our point of
> view, it is u-Boot which is too complex and should drop its uImage
> complexity.

Insisting without giving explanations about the reasons is not exactly
a constructive form of a discussion. Actually it is no discussion at
all.

> But instead of asking you to drop u-Boot's complexity, I'm only asking
> for u-Boot to let both methods to coexist and work.

Ok, we can make a deal on such a base. See the suggestion inmy
previous message.

> Given that the zImage "complexity" is not going away because we insist
> on keeping it, either we find a middle ground such as Stephen's patches,
> or we advocate for a different bootloader on ARM.
>
> Do you never happend to compromize once in a while?

In my understanding, compromize is not a one-sided business.

It is actually easy to convince me, but it needs facts and arguments,
not mere insisting on preconceived statements or plain extortion.

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
The shortest unit of time in the multiverse is the News York Second,
defined as the period of time between the traffic lights turning
green and the cab behind you honking.
- Terry Pratchett, _Lords and Ladies_