From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Bob Mende Pie <mende@piecomputer.engr.sgi.com>
Cc: ralf@Julia.DE, ariel@sgi.com, linux@yon.engr.sgi.com
Subject: Re: Merge back of the MIPS sources
Date: Mon, 9 Jun 1997 11:36:10 -0700 [thread overview]
Message-ID: <199706091836.LAA02114@fir.engr.sgi.com> (raw)
In-Reply-To: <199706061807.LAA01554@piecomputer.engr.sgi.com>
Bob Mende Pie writes:
> Ralf,
>
> Have you verified that the newest code still works on the other MIPS
> based systems? Also, is it possible to have (linux) binary compatability
> between a mips Magnum or Millennium and an Indy?
> There is a 50Mhz Millennium over here that we might be able to use as a
> test system.
If the MIPS system is running big-endian (as under RISCos), it can
be binary-compatible with Indy linux, just as RISCos 5.01 -systype svr4
binaries are binary-compatible with Indy IRIX 5.1 and later systems.
If the MIPS system is running little-endian (as under NT), it cannot
be binary-compatible with Indy linux, without adding bi-endian support
(for running opposite-endian binaries, which is feasible, but messy).
We prototyped bi-endian support in RISCos when before the Magnum
was built, and it worked, but the code was very ugly in the streams
area. linux would likely be easier, but still a hassle.
next prev parent reply other threads:[~1997-06-09 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-06 15:27 Merge back of the MIPS sources Ralf Baechle
1997-06-06 17:31 ` Ariel Faigon
1997-06-06 17:32 ` Ralf Baechle
1997-06-06 18:07 ` Bob Mende Pie
1997-06-06 18:36 ` Ralf Baechle
1997-06-06 18:36 ` Ralf Baechle
1997-06-09 18:42 ` William J. Earl
1997-06-09 18:42 ` William J. Earl
1997-06-09 18:36 ` William J. Earl [this message]
1997-06-10 10:59 ` Ralf Baechle
1997-06-10 10:59 ` Ralf Baechle
1997-06-10 17:48 ` William J. Earl
1997-06-10 20:22 ` Ralf Baechle
1997-06-10 20:22 ` 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=199706091836.LAA02114@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=ariel@sgi.com \
--cc=linux@yon.engr.sgi.com \
--cc=mende@piecomputer.engr.sgi.com \
--cc=ralf@Julia.DE \
/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