Hi!

quoted text
> > > The resulting kernel hasn't broken on me yet, however.
> > > 
> > > A search through the LKML archives showed that this was reported
> > > for 2.6.25-rc3-mm1, but I couldn't find any discussion about it
> > > after that:
> > > 
> > > <http://marc.info/?l=linux-kernel&m=120470303728010&w=2>
> > > 
> > > The .config causing this warning is available in
> > > <http://user.it.uu.se/~mikpe/linux/ale/config-2.6.26-rc1>
> > > 
> > 
> > This is because the organization of the file was changed, and the linker 
> > script wasn't changed to match:
> > 
> > SECTIONS
> > {
> >          . = HEADER_OFFSET;
> >          .header : {
> >                   *(.header)
> >          }
> > 
> >          . = 0;
> >          .text : {
> >                   *(.text*)
> >          }
> > 
> > This is crap; the sections should be listed *in order* so the linker can 
> > warn properly when something bad happens.
> > 
> > The code should be correct; reorganizing the linker script correctly 
> > should fix the problem.

I'm not good at linker magic. I needed to put code from offset zero,
while still having header at known address...

quoted text
> Hm.  The above is from Pavel and Sam.

Sorry about that. Plus, I'm on holidays just now...

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/