From: Neil Russell <caret@c-side.com>
To: David Riley <oscar@the-rileys.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC byte ordering
Date: Sat, 28 Oct 2000 17:24:51 -0700 [thread overview]
Message-ID: <20001028172451.A10220@lx.c-side.com> (raw)
In-Reply-To: <39FB3C16.3359BC41@the-rileys.net>; from David Riley on Sat, Oct 28, 2000 at 04:50:38PM -0400
Some PPC CPUs don't implement all load/store instructions for little
endian; for instance, the 603 CPUs don't do lmw, stmw, lswi, lswx,
stswi, stswx for little endian. I seem to remember that there are other
problems aside from the ones that I mentioned. Later CPUs don't seem
to have a problem.
It would in theory be possible to have the kernel run big-endian as it is
and have certain user programs run little endian by setting the LE bit in
the MSR register for the process in question. The real problem here is
that you have to add a *lot* of code to system calls to make this work.
There are a few system calls that this would be real difficult, such
as ioctl(). I once looked into doing this for the MIPS with SVR4 UNIX.
Neil.
On Sat, Oct 28, 2000 at 04:50:38PM -0400, David Riley wrote:
> Before I get dirty looks, I know the PowerPC's default byte ordering is
> big-endian (the way things *should* be :-). What I'm asking is slightly
> irrelevant to most development discussion here, but...
>
> I know that the PowerPC does allow both endian modes. My big question
> is how well it works in little endian mode. I know we'll never switch
> Linux to this, since that would be too much unnecessary work, but just
> for reference: Is it broken? I have heard reports to this effect.
>
> Thanks,
> David
>
--
Neil Russell <caret@c-side.com>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-29 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-28 20:50 PPC byte ordering David Riley
2000-10-29 0:24 ` Neil Russell [this message]
2000-10-30 9:12 ` Timothy A. Seufert
2000-07-19 13:59 ` Heiko Jakob
2000-10-30 12:50 ` Gabriel Paubert
2000-10-30 12:18 ` Geert Uytterhoeven
2000-10-31 11:23 ` Timothy A. Seufert
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=20001028172451.A10220@lx.c-side.com \
--to=caret@c-side.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=oscar@the-rileys.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;
as well as URLs for NNTP newsgroup(s).