linux-mips
[Top] [All Lists]

Re: scope of this mailing list

To: Ralf Baechle <ralf@informatik.uni-koblenz.de>
Subject: Re: scope of this mailing list
From: wje@fir.esd.sgi.com (William J. Earl)
Date: Wed, 1 May 1996 08:44:55 -0700
Cc: ewt@redhat.com (Erik Troan), linux@neteng.engr.sgi.com
In-reply-to: <199605010233.EAA26130@informatik.uni-koblenz.de>
References: <Pine.LNX.3.91.960429200526.3781C-100000@redhat.com> <199605010233.EAA26130@informatik.uni-koblenz.de>
Sender: owner-linux@cthulhu.engr.sgi.com
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.

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