From: Pete Popov <ppopov@mvista.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Endianness...
Date: Wed, 02 May 2001 13:52:21 -0700 [thread overview]
Message-ID: <3AF07385.22E94902@mvista.com> (raw)
In-Reply-To: NEBBLJGMNKKEEMNLHGAIGEEFCBAA.mdharm@momenco.com
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.
I saw some of the replies. I don't think it's true that BE is "the" way
to go. mips-linux runs both, le and be. We have three different LE
boards and our partners have shipped our LE port to many of their
customers. The Alchemy board I'm working on runs both, LE and BE and
I've tested both. Depending on the peripherals you want to support,
like USB, PCMCIA, etc, little endian might be a lot easier to port to.
If on the other hand you're interested in a mips64 smp port, then BE is
probably the easiest way to go because of the current support of
mips64. As far as binary completeness, the RedHat 7.0 port is, I think,
BE. But our HardHat Linux 2.0 will offer the same completeness for both,
LE and BE (should be on the ftp site by the end of the month).
Pete
next prev parent reply other threads:[~2001-05-02 20:55 UTC|newest]
Thread overview: 8+ 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 ` Endianness Kevin D. Kissell
2001-05-02 20:52 ` Pete Popov [this message]
2001-05-03 6:47 ` Endianness Houten K.H.C. van (Karel)
-- strict thread matches above, loose matches on Subject: below --
2001-05-03 9:47 endianness Didier Kryn
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=3AF07385.22E94902@mvista.com \
--to=ppopov@mvista.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 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.