[okl4-developer] OKL4 v2.1: Building an XIP image

[Frank Kaiser]

Hi, Geoffrey

Got it. My statement was based on the allocation address of the
'kernel.data' section. However, a glance into
'arch/arm/pistachio/src/gnu/linker.lds' shows that the address pointer
is shifted by 256 before anything is allocated into the '.data' section,
when CONFIG_XIP is set. Hence my concern seems to be obsolete.
By the way, I see nothing similar in the RVCT version of the linker
script.

Regards
Frank
> -----Original Message-----
> From: Geoffrey Lee [mailto:glee at ok-labs.com]
> Sent: Thursday, August 28, 2008 5:20 PM
> To: Frank Kaiser
> Cc: developer at okl4.org
> Subject: Re: [okl4-developer] OKL4 v2.1: Building an XIP image
> 
> On Wed, Aug 27, 2008 at 04:56:01PM +0200, Frank Kaiser wrote:
> > Hello
> >
> 
> 
> Hi Frank
> 
> >
> > Another problem is the allocation of the kernel.data section. Its
> > position at the start of the RAM results in a clash with the ARM
globals
> > which are hard-wired to the start address of the RAM. I mentioned
this a
> > while ago
> >
(http://n2.nabble.com/Re%3A-OKL4-v2.1%3A-ARM-startup-code-overwrites-its
> > elf-tp219821p219821.html), and it was said that space will be
reserved
> > for the ARM globals. The above list does not give an indication that
> > this is the case.
> 
> Space really is reserved for the arm globals even in the case of XIP.
> This is done in the linker script.  Have you noticed suspicious
> behavior, or is this by inspection of the bootable image?
> 
> 
> >
> >
> >
> > Regards
> >
> > Frank
> 
> 	-gl
> 
> >
> 
> > _______________________________________________
> > Developer mailing list
> > Developer at okl4.org
> > https://lists.okl4.org/mailman/listinfo/developer
> 
> 
> --