From: "Heiko Jakob" <buffalo@the7lg.de>
To: "Neil Russell" <caret@c-side.com>,
"David Riley" <oscar@the-rileys.net>,
<linuxppc-dev@lists.linuxppc.org>,
"Timothy A. Seufert" <tas@mindspring.com>
Subject: Re: PPC byte ordering
Date: Wed, 19 Jul 2000 15:59:43 +0200 [thread overview]
Message-ID: <003101bff189$9ac1f800$084da8c0@uranus> (raw)
In-Reply-To: v04220803b622eb4a1108@[10.0.0.42]
> At 5:24 PM -0700 10/28/00, Neil Russell wrote:
>
> >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.
>
> The other real problem is that Linus Torvalds has already said that
> he will never ever in a million years accept a patch which attempts
> to do such a thing, so you'd have to fork the kernel to do it.
> According to Linus, architectures are either big or little-endian,
> not both. A sane position considering the syscall ugliness you
> mention
How do the linux-mips people handle with big- and little-endian code ?
Maybe they know a good solution, which allows both big- and little-endian
code to execute.
The PPC is big-endian by nature, and what for we do need little-endian code
to be executed on a PPC ?
MfG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-19 13:59 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
2000-10-30 9:12 ` Timothy A. Seufert
2000-07-19 13:59 ` Heiko Jakob [this message]
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='003101bff189$9ac1f800$084da8c0@uranus' \
--to=buffalo@the7lg.de \
--cc=caret@c-side.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=oscar@the-rileys.net \
--cc=tas@mindspring.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.