From: wje@fir.esd.sgi.com (William J. Earl)
To: Ralf Baechle <ralf@informatik.uni-koblenz.de>
Cc: ewt@redhat.com (Erik Troan), linux@neteng.engr.sgi.com
Subject: Re: scope of this mailing list
Date: Wed, 1 May 1996 08:44:55 -0700 [thread overview]
Message-ID: <199605011544.IAA07701@fir.esd.sgi.com> (raw)
In-Reply-To: <199605010233.EAA26130@informatik.uni-koblenz.de>
Ralf Baechle writes:
...
> The main issue in achieving binary compatibility accross all Linux/MIPS
> targets is the byte order. For some machines (Mips Magnum 4000, Olivetti
> M700-10, SNI RM series and others more) the byte order for the kernel is
> configurable. For other it is fixed. This is often the case for machines
> that were built with NT in mind.
>
> The MIPS architecture offers us the nice feature of switchable byteorder
> for usermode. Thus we have a way to run software from other systems with
> differing native byte order. In other words: it's technological possible
> but it's not implemented yet.
...
I once worked on this problem on another OS base. The basic system
calls are easy. ioctls, especially for streams, were much harder. Within
the limits of the published ABI, as opposed to the universe of working programs,
the task is not too difficult.
WARNING: multiple messages have this Message-ID (diff)
From: wje@fir.esd.sgi.com (William J. Earl)
To: Ralf Baechle <ralf@informatik.uni-koblenz.de>
Cc: Erik Troan <ewt@redhat.com>, linux@neteng.engr.sgi.com
Subject: Re: scope of this mailing list
Date: Wed, 1 May 1996 08:44:55 -0700 [thread overview]
Message-ID: <199605011544.IAA07701@fir.esd.sgi.com> (raw)
Message-ID: <19960501154455.CVmhxrYPdxc2eBgTaFB7swEhJUQMol7_nFpReZzKT3I@z> (raw)
In-Reply-To: <199605010233.EAA26130@informatik.uni-koblenz.de>
Ralf Baechle writes:
...
> The main issue in achieving binary compatibility accross all Linux/MIPS
> targets is the byte order. For some machines (Mips Magnum 4000, Olivetti
> M700-10, SNI RM series and others more) the byte order for the kernel is
> configurable. For other it is fixed. This is often the case for machines
> that were built with NT in mind.
>
> The MIPS architecture offers us the nice feature of switchable byteorder
> for usermode. Thus we have a way to run software from other systems with
> differing native byte order. In other words: it's technological possible
> but it's not implemented yet.
...
I once worked on this problem on another OS base. The basic system
calls are easy. ioctls, especially for streams, were much harder. Within
the limits of the published ABI, as opposed to the universe of working programs,
the task is not too difficult.
next prev parent reply other threads:[~1996-05-01 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-29 23:27 scope of this mailing list Larry McVoy
1996-04-30 0:06 ` Erik Troan
1996-05-01 2:30 ` Ralf Baechle
1996-05-01 2:30 ` Ralf Baechle
1996-05-01 15:44 ` William J. Earl [this message]
1996-05-01 15:44 ` William J. Earl
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=199605011544.IAA07701@fir.esd.sgi.com \
--to=wje@fir.esd.sgi.com \
--cc=ewt@redhat.com \
--cc=linux@neteng.engr.sgi.com \
--cc=ralf@informatik.uni-koblenz.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 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.