linux-mips
[Top] [All Lists]

Re: No bzImage target for MIPS

To: Karsten Merker <karsten@excalibur.cologne.de>
Subject: Re: No bzImage target for MIPS
From: Keith Owens <kaos@melbourne.sgi.com>
Date: Sat, 15 Dec 2001 20:14:59 +1100
Cc: linux-mips@oss.sgi.com
In-reply-to: Your message of "Sat, 15 Dec 2001 09:31:01 BST." <20011215093101.A256@excalibur.cologne.de>
Sender: owner-linux-mips@oss.sgi.com
On Sat, 15 Dec 2001 09:31:01 +0100, 
Karsten Merker <karsten@excalibur.cologne.de> wrote:
>On Fri, Dec 14, 2001 at 10:52:57AM -0800, Geoffrey Espin wrote:
>> BTW, does any actually build 'vmlinux.ecoff'?
>
>Yes, it is (among other uses) the default target for DECstations,
>the DECstation firmware cannot tftp-boot anything else.

I am standardizing the list of supported formats for linux boot, as
part of the kbuild 2.5 rewrite, I will add vmlinux.ecoff to the master
list.

AFAICT ecoff is only used on mips but, since ecoff is not an arch
specific object format, it makes sense to make it a generic kbuild
target, like elf, srec and bin.  To that end, I looked at moving
elf2ecoff and addinitrd to an arch independent directory so everybody
could use those tools, alas both contain mips specific code.  Any idea
how much work is required to make elf2ecoff and addinitrd into generic
utilities?  Is it worth the effort or should they stay as mips only?


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