From: Dan Malek <dan@mvista.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linuxppc-embedded@lists.linuxppc.org, cort@fsmlabs.com,
Alexandre.Nikolaev@matrox.com
Subject: Re: ppc little-endian port
Date: Mon, 30 Apr 2001 13:15:36 -0400 [thread overview]
Message-ID: <3AED9DB8.7B15F60D@mvista.com> (raw)
In-Reply-To: 200104282316.f3SNG7D365341@saturn.cs.uml.edu
"Albert D. Cahalan" wrote:
> I'm going to tackle it. Alexandre Nikolaev already is tackling
> it I guess.
That's way beyond the scope of discussion or interest on this
list. Make sure you contact the proper tools, library, and
application folks.
> Lots of PowerPC processors run in little-endian mode today.
Lots? Maybe a few. Since the first days of PowerPC I have only
seen one ill-fated attempt. Every time I'm part of a PPC silicon
design discussion the question is always raised whether it is
worth wasting silicon trying to support it.
It's getting harder to use little endian on PowerPC. The 7450 has
only a big endian bus, with some weird lane swapping internally.
Misaligned little endian accesses still cause processor exceptions,
and the 7450 states it doesn't support it at all (some contradiction
here), so you are always at a performance disadvantage when using
it. Besides, the bytes are all backward from the normal order of
the world and you end up spending cycles swapping them, anyway :-).
> .... Modern medical scanners (CAT, MRI, PET...)
> all use little-endian PowerPC processors.
It can't be all, because I have worked on some prototypes in the
past that weren't.
> Opinions on this don't matter when you put a 7400 on a PCI board
> and try to share memory with an x86 host computer.
My opinions always matter :-). In this case you should be using
a big-endian PowerPC host computer, too.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-30 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 23:16 ppc little-endian port Albert D. Cahalan
2001-04-30 17:15 ` Dan Malek [this message]
2001-04-30 18:15 ` Ralph Blach
2001-04-30 20:38 ` Cort Dougan
2001-04-30 22:14 ` Albert D. Cahalan
2001-04-30 22:44 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2001-04-25 12:16 Zehetbauer Thomas
2001-04-23 18:58 Alexandre Nikolaev
2001-04-24 0:15 ` Cort Dougan
2001-04-24 2:47 ` Dan Malek
2001-04-24 10:11 ` Gabriel Paubert
[not found] ` <3AE5595C.74644FE5@raleigh.ibm.com>
2001-04-24 14:38 ` Alexandre Nikolaev
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=3AED9DB8.7B15F60D@mvista.com \
--to=dan@mvista.com \
--cc=Alexandre.Nikolaev@matrox.com \
--cc=acahalan@cs.uml.edu \
--cc=cort@fsmlabs.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).