From: Troy Benjegerdes <hozer@drgw.net>
To: Zehetbauer Thomas <TZ@link.topcall.co.at>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: IBM PPC 405 series little endian?
Date: Mon, 11 Jun 2001 13:39:49 -0500 [thread overview]
Message-ID: <20010611133949.Q753@altus.drgw.net> (raw)
In-Reply-To: <41EA756DBC9FD0118CFC0020AFDB5C5A188DE7@tcint1ntsrv>
In-Reply-To: <41EA756DBC9FD0118CFC0020AFDB5C5A188DE7@tcint1ntsrv>; from TZ@link.topcall.co.at on Mon, Jun 11, 2001 at 01:34:21PM +0200
On Mon, Jun 11, 2001 at 01:34:21PM +0200, Zehetbauer Thomas wrote:
> Has someone experimented with running linux in little-endian mode on IBM
> PowerPC 405 (Walnut) yet?
Well, first, I have to ask, why??
First, if you need to deal with little endian data, on a PPC stwbrx &
lwbrx are your friends.
With the possible exception of the matrox guy, I haven't heard of ANYONE
running in LE mode on ppc. The second problem is going to be to recompile
ALL the applications you want and hope they work.
Finally, if you're doing anything that connects to the internet, remember
that network byte order is big-endian. You might find it interesting that
even Intel is now re-discovering the usefullness of big-endian in some of
their strongarm/Xscale processors.
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Shulz
next prev parent reply other threads:[~2001-06-11 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 11:34 IBM PPC 405 series little endian? Zehetbauer Thomas
2001-06-11 18:18 ` Albert D. Cahalan
2001-06-11 18:39 ` Troy Benjegerdes [this message]
2001-06-11 19:08 ` Mark Salisbury
2001-06-12 1:39 ` Troy Benjegerdes
-- strict thread matches above, loose matches on Subject: below --
2001-06-11 19:53 Marti, Felix
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=20010611133949.Q753@altus.drgw.net \
--to=hozer@drgw.net \
--cc=TZ@link.topcall.co.at \
--cc=linux-kernel@vger.kernel.org \
/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