From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: Keith Owens <kaos@melbourne.sgi.com>,
Karsten Merker <karsten@excalibur.cologne.de>,
linux-mips@oss.sgi.com
Subject: Re: No bzImage target for MIPS
Date: Mon, 17 Dec 2001 18:32:49 -0200 [thread overview]
Message-ID: <20011217183249.A2081@dea.linux-mips.net> (raw)
In-Reply-To: <20011215124604.GE23167@paradigm.rfc822.org>; from flo@rfc822.org on Sat, Dec 15, 2001 at 01:46:04PM +0100
On Sat, Dec 15, 2001 at 01:46:04PM +0100, Florian Lohoff wrote:
> > 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?
>
> Last i had a look elf2ecoff and addinitrd were not really nice
> recovering from toolchain problems like pages of null between sections
> which was a common fault a couple months back. This lead to addinitrd
> not beeing able to attach a ramdisk that the kernel would be able to
> find it.
>
> BTW: Shouldn't objcopy be able to convert an ELF into an ECOFF ?
In theory yes, in practice that was found to be so problematic that we
just gave up and use those NetBSD tools.
Ralf
next prev parent reply other threads:[~2001-12-17 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 0:47 No bzImage target for MIPS Krishna Kondaka
2001-12-14 1:10 ` Pete Popov
2001-12-14 3:28 ` Geoffrey Espin
2001-12-14 3:51 ` Keith Owens
2001-12-14 4:12 ` Geoffrey Espin
2001-12-14 18:05 ` Pete Popov
2001-12-14 18:52 ` Geoffrey Espin
2001-12-14 19:11 ` Pete Popov
2001-12-15 8:31 ` Karsten Merker
2001-12-15 9:14 ` Keith Owens
2001-12-15 12:46 ` Florian Lohoff
2001-12-17 20:32 ` Ralf Baechle [this message]
2001-12-17 13:12 ` Maciej W. Rozycki
2001-12-15 12:42 ` Florian Lohoff
-- strict thread matches above, loose matches on Subject: below --
2001-12-14 0:55 Marc Karasek
2001-12-14 22:59 Marc Karasek
2001-12-14 23:42 ` Pete Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011217183249.A2081@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=kaos@melbourne.sgi.com \
--cc=karsten@excalibur.cologne.de \
--cc=linux-mips@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox