Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: nick@snowman.net
Cc: Matthew Dharm <mdharm@momenco.com>, Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: Endianness...
Date: Wed, 02 May 2001 13:47:07 -0700	[thread overview]
Message-ID: <3AF0724B.D74D9AF9@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.21.0105021603030.22170-100000@ns

nick@snowman.net wrote:
> 
> To the best of my knowledge Big endian is generally the way to run.
>         Nick
> 

BE is better known perhaps because all SGI workstations are BE.  Generally I
found networking systems tend to use BE while consumer electronic devices tend
to use LE (which means there are probably more MIPS CPUs running in LE.)

So far I have not found much difference in terms of endianess, although
occassionaly you have to IO swap in drivers for BE machine.

Jun

> On Wed, 2 May 2001, Matthew Dharm wrote:
> 
> > What's the preferred endianness for Linux-MIPS?  I can't really go
> > into why I'm asking (sensitive NDA information), but I'm basically
> > faced with a group that wants to work in LE.  However, my
> > understanding was that Linux-MIPS generally ran BE.
> >
> > Or can it be built either way?  I know OpenBSD runs LE.... not like
> > that means anything to this group, tho.
> >
> > Matt Dharm
> >
> > --
> > Matthew D. Dharm                            Senior Software Designer
> > Momentum Computer Inc.                      1815 Aston Ave.  Suite 107
> > (760) 431-8663 X-115                        Carlsbad, CA 92008-7310
> > Momentum Works For You                      www.momenco.com
> >

  reply	other threads:[~2001-05-02 20:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 20:01 Endianness Matthew Dharm
2001-05-02 20:03 ` Endianness nick
2001-05-02 20:47   ` Jun Sun [this message]
2001-05-04 12:46     ` Endianness Ralf Baechle
2001-05-02 20:21 ` Endianness Kevin D. Kissell
2001-05-02 20:52 ` Endianness Pete Popov
2001-05-03  6:47   ` Endianness Houten K.H.C. van (Karel)

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=3AF0724B.D74D9AF9@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.com \
    --cc=nick@snowman.net \
    /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