public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: David Riley <oscar@the-rileys•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: PPC byte ordering
Date: Sat, 28 Oct 2000 16:50:38 -0400	[thread overview]
Message-ID: <39FB3C16.3359BC41@the-rileys.net> (raw)


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

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-10-28 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-28 20:50 David Riley [this message]
2000-10-29  0:24 ` PPC byte ordering Neil Russell
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=39FB3C16.3359BC41@the-rileys.net \
    --to=oscar@the-rileys$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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