linux-mips
[Top] [All Lists]

Re: [RFC] Add __initbss section

To: Thiemo Seufer <ths@networkno.de>
Subject: Re: [RFC] Add __initbss section
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Thu, 11 Oct 2007 17:16:45 +0100 (BST)
Cc: Franck Bui-Huu <vagabon.xyz@gmail.com>, Ralf Baechle <ralf@linux-mips.org>, Geert Uytterhoeven <geert@linux-m68k.org>, linux-mips <linux-mips@linux-mips.org>
In-reply-to: <20071011152615.GE3379@networkno.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <470DF25E.60009@gmail.com> <20071011152615.GE3379@networkno.de>
Sender: linux-mips-bounce@linux-mips.org
On Thu, 11 Oct 2007, Thiemo Seufer wrote:

> > Also not that with the current patchset applied, there are now 2
> > segments that need to be loaded, hopefully it won't cause any issues
> > with any bootloaders out there that would assume that an image has
> > only one segment...
> 
> This breaks at least conversion to ECOFF as used on DECstations.

 Indeed, thanks for pointing it out -- I use ELF over MOP and keep 
forgetting about people preferring TFTP, sigh.  I wonder whether `objcopy' 
might be doing a better job than `elf2ecoff' these days though.  It may be 
worth checking...

 It all boils down to padding out what cannot be expressed in a less 
capable format after all.  That's what I did in `mopd' for ELF support too 
-- holes between segments are transmitted as zeroes.  Though MOP clients 
may actually support discontiguous images as each MOP "downline load" 
packet has its designated memory load address included in the header (it 
just shows how reasonable a bootstrap protocol it is!).

  Maciej

<Prev in Thread] Current Thread [Next in Thread>