[PATCHv3] ARM:boot:device tree: Allow the device tree binary to be appended to zImage

Nicolas Pitre nico at fluxnic.net
Fri Apr 29 09:21:22 EDT 2011


On Fri, 29 Apr 2011, Tony Lindgren wrote:

> * Grant Likely <grant.likely at secretlab.ca> [110429 05:59]:
> > On Fri, Apr 29, 2011 at 4:26 AM, Tony Lindgren <tony at atomide.com> wrote:
> > > * Tony Lindgren <tony at atomide.com> [110427 07:41]:
> > >
> > > If the compressed image is smaller than BSS, then we end up
> > > having DT data in the BSS area. In this case the compressed
> > > image is about 2.3 MB for LZMA.
> > >
> > > The uncompress code does not know about the kernel BSS,
> > > and does not necessarily relocate anything depending on the
> > > compressed image load address.
> > >
> > > So in which code do we want to relocate the DT data?
> > >
> > > We could do it based on estimated BSS size in uncompress code,
> > > or based on the real BSS size in __mmap_switched before BSS
> > > gets reset.
> > 
> > How about telling the wrapper what the final size will be by scraping
> > the __bss_end value out of System.map?
> 
> That sounds doable to me. It should probably be done in the uncompress
> code so the kernel code can stay generic for the DT data handling.

Well, that's probably doable too.  If the final kernel's .bss conflicts 
with the DT data, then moving the DT data above the malloc space in the 
decompressor is trivial too.


Nicolas



More information about the linux-arm-kernel mailing list