All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@Julia.DE>
To: wje@fir.esd.sgi.com (William J. Earl)
Cc: shaver@neon.ingenia.ca, linux@cthulhu.engr.sgi.com
Subject: Re: serial consoles, sash and other wonders
Date: Wed, 9 Apr 1997 12:06:52 +0200 (MET DST)	[thread overview]
Message-ID: <199704091006.MAA06864@kernel.panic.julia.de> (raw)
In-Reply-To: <199704081948.MAA14047@fir.esd.sgi.com> from "William J. Earl" at Apr 8, 97 12:48:07 pm

Hi,

>      By the way, it is pretty easy to write a little program to convert
> a kernel ELF binary to an ECOFF binary, discarding most of the symbols and
> other stuff, assuming you have the header files for the file formats.
> (The result would not be acceptable to many of the tools, such as dbx,
> but it would be bootable.)
> 
>      For a production linux for the Indy, the most reasonable approach,
> however, would be to make silo or whatever boot program you are using be
> ECOFF, so that old PROMs are supported.

I also have to deal with ARC machines (the little endian NT stuff).  By
definiton they have to support ECOFF; everything else is optional.  This
brings in the extra issue that the loader needs to be relocatable.
MIPS-ECOFF configurations of GCC can't do that and the linker dies when
loading ELF PIC code into an ECOFF executable.  Unfortunately fixing is
nontrivial.

The {Net,Open}BSD people already have a converter tool which they use to
generate their kernel executable.  It would solve the ld problems.
I did some work on it and I should probably finish it ...

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@Julia.DE>
To: "William J. Earl" <wje@fir.esd.sgi.com>
Cc: shaver@neon.ingenia.ca, linux@cthulhu.engr.sgi.com
Subject: Re: serial consoles, sash and other wonders
Date: Wed, 9 Apr 1997 12:06:52 +0200 (MET DST)	[thread overview]
Message-ID: <199704091006.MAA06864@kernel.panic.julia.de> (raw)
Message-ID: <19970409100652.qcoXEh2iNAa_ic1IoscLGK06c2I6QJ8uWWrNVWrOh9k@z> (raw)
In-Reply-To: <199704081948.MAA14047@fir.esd.sgi.com> from "William J. Earl" at Apr 8, 97 12:48:07 pm

Hi,

>      By the way, it is pretty easy to write a little program to convert
> a kernel ELF binary to an ECOFF binary, discarding most of the symbols and
> other stuff, assuming you have the header files for the file formats.
> (The result would not be acceptable to many of the tools, such as dbx,
> but it would be bootable.)
> 
>      For a production linux for the Indy, the most reasonable approach,
> however, would be to make silo or whatever boot program you are using be
> ECOFF, so that old PROMs are supported.

I also have to deal with ARC machines (the little endian NT stuff).  By
definiton they have to support ECOFF; everything else is optional.  This
brings in the extra issue that the loader needs to be relocatable.
MIPS-ECOFF configurations of GCC can't do that and the linker dies when
loading ELF PIC code into an ECOFF executable.  Unfortunately fixing is
nontrivial.

The {Net,Open}BSD people already have a converter tool which they use to
generate their kernel executable.  It would solve the ld problems.
I did some work on it and I should probably finish it ...

  Ralf

  parent reply	other threads:[~1997-04-09 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-08 19:03 serial consoles, sash and other wonders Mike Shaver
1997-04-08 19:26 ` Ariel Faigon
1997-04-08 19:26   ` Ariel Faigon
1997-04-08 19:48 ` William J. Earl
1997-04-08 21:31   ` Mike Shaver
1997-04-08 21:31     ` Mike Shaver
1997-04-08 22:00     ` William J. Earl
1997-04-08 22:00       ` William J. Earl
1997-04-09 10:06   ` Ralf Baechle [this message]
1997-04-09 10:06     ` Ralf Baechle

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=199704091006.MAA06864@kernel.panic.julia.de \
    --to=ralf@julia.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=shaver@neon.ingenia.ca \
    --cc=wje@fir.esd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.