lkml.org 
[lkml]   [2011]   [Oct]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] arm/tegra: select AUTO_ZRELADDR by default
On Fri, 14 Oct 2011, Russell King - ARM Linux wrote:

> On Fri, Oct 14, 2011 at 04:14:12PM -0400, Nicolas Pitre wrote:
> > On Fri, 14 Oct 2011, Russell King - ARM Linux wrote:
> >
> > > On Fri, Oct 14, 2011 at 02:01:07PM -0400, Nicolas Pitre wrote:
> > > > The way I'm restructuring things around this is that AUTO_ZRELADDR will
> > > > always be active by default, just like ARM_PATCH_PHYS_VIRT now. This
> > > > platform specific exclusion thinking is a step backward so I'd prefer if
> > > > people would refrain from going there for the moment.
> > >
> > > Are you expecting everyone to change the way they load the zImage
> > > overnight then?
> >
> > No, of course. But adding restrictions in the kernel build because
> > u-Boot's own image format dictates such restrictions doesn't make sense.
> > Those restrictions must be pushed towards the uImage encapsulation step,
> > not higher the kernel config hierarchy.
>
> You're not understanding again.
>
> I'm talking about people who _explicitly_ load the zImage at a different
> address to which the decompressed image ends up. With AUTO_ZRELADDR=y
> their setup will break unless they stop that behaviour, which takes
> away one of the advantages of using the zImage format.

Would you care to explain where you got this from? Because I really do
not understand what you're saying indeed.

With AUTO_ZRELADDR=y you _still_ can load zImage to a different location
from where the decompressed kernel ends up.


Nicolas


\
 
 \ /
  Last update: 2011-10-14 22:33    [W:0.497 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site