From: "Kevin D. Kissell" <kevink@mips.com>
To: "Matthew Dharm" <mdharm@momenco.com>,
"Linux-MIPS" <linux-mips@oss.sgi.com>
Subject: Re: Endianness...
Date: Wed, 2 May 2001 22:21:58 +0200 [thread overview]
Message-ID: <018301c0d345$8f56abc0$0deca8c0@Ulysses> (raw)
In-Reply-To: NEBBLJGMNKKEEMNLHGAIGEEFCBAA.mdharm@momenco.com
I have one machine set up each way, an Algorithmics
P5064/R5260 running LE on a 2.2.12 kernel and a
MIPS Malta/4KC running BE under 2.4.1. There are pros
and cons. On one hand, most of the "bleeding edge"
work is only tested on BE SGI platforms before being
checked-in, and the BE userland binary distributions
are more complete. On the other hand, it's generally
easier to port drivers for x86-oriented peripherals to
a LE kernel.
Regards,
Kevin K.
----- Original Message -----
From: "Matthew Dharm" <mdharm@momenco.com>
To: "Linux-MIPS" <linux-mips@oss.sgi.com>
Sent: Wednesday, May 02, 2001 10:01 PM
Subject: Endianness...
> 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
>
next prev parent reply other threads:[~2001-05-02 20:17 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 ` Endianness Jun Sun
2001-05-04 12:46 ` Endianness Ralf Baechle
2001-05-02 20:21 ` Kevin D. Kissell [this message]
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='018301c0d345$8f56abc0$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox