All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salisbury <mbs@mc.com>
To: Holger Bettag <hobold@Informatik.Uni-Bremen.DE>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: ppc LE questions (seeking help hand info pointers)
Date: Thu, 20 Sep 2001 16:19:18 -0400	[thread overview]
Message-ID: <3BAA4F46.1020002@mc.com> (raw)
In-Reply-To: 8xlmj9psnw.fsf@s62.informatik.uni-bremen.de


Holger Bettag wrote:

> Mark Salisbury <mbs@mc.com> writes:
>
> [... linux in ppc little endian mode ...]
>
>>well, this is in the context of a multi-CPU type (x86/ppc, sparc/ppc,
>>ppc/ppc, mips/ppc) shared memory multicomputer.
>>
>>when dealing w/ direct mapped, shared memory, uniformity of endian-ness
>>makes many multicomputer problems easier to solve.(not to mention easier
>>for the customer to program...)
>>
>>
> You are aware that a PPC in little endian mode is merely tricking with the
> low order address bits, but does not actually lay out its data in a little
> endian fashion in physical memory?
>

not according to section 3.1 of the motorola ppc "green book"

according to that it is a sort of munged le representation,

which thanks to a "one trick pony" PCI bridge looks like standard LE to
the PCI based  x86 host.

understand please that what I am proposing is a config option. as a
sub-architecture port.  it would not affect any code that it didn't
absolutely need to, and would only be compiled if sombody selected that
particular config.

I am _NOT_ suggesting running pmacs in LE mode.

as in:
ppc---
      |-- PREP
      |-- CHRP
      |-- MAC
      |-- MERCURY ---
                    |-- Big Endian
                    |-- Little Endian






--
/*------------------------------------------------**
**   Mark Salisbury | Mercury Computer Systems    **
**   mbs@mc.com     | System OS - Kernel Team     **
**------------------------------------------------**
**         Infinite Justice is niether.           **
**------------------------------------------------*/


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

  parent reply	other threads:[~2001-09-20 20:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 15:42 ppc LE questions (seeking help hand info pointers) Mark Salisbury
2001-09-20 15:58 ` Tom Rini
2001-09-20 16:07   ` Geert Uytterhoeven
2001-09-20 16:12     ` Tom Rini
2001-09-20 17:10       ` Brad Boyer
2001-09-20 18:32         ` Mark Salisbury
2001-09-20 19:29           ` Holger Bettag
2001-09-20 19:35             ` David Edelsohn
2001-09-20 20:19             ` Mark Salisbury [this message]
2001-09-21  1:46               ` Timothy A. Seufert
2001-09-21  3:54                 ` Dan Malek
2001-09-21  7:24                   ` Geert Uytterhoeven
2001-09-21  7:47                     ` Dan Malek
2001-09-21  7:50                       ` Geert Uytterhoeven
2001-09-21  8:19                         ` Dan Malek
2001-09-21 17:01                   ` Ralph Blach
2001-09-21 17:35                     ` David Edelsohn
2001-09-21 18:58                     ` David Edelsohn
2001-09-21 20:22                     ` Dan Malek
2001-09-21 20:29                     ` Benjamin Herrenschmidt
2001-09-21 20:42                       ` Benjamin Herrenschmidt
2001-09-21  7:22                 ` Geert Uytterhoeven
2001-09-21  9:26               ` keyb Giuliano Pochini
2001-09-21 10:38             ` ppc LE questions (seeking help hand info pointers) Ralph Blach
2001-09-20 20:01           ` Tony Mantler
2001-09-20 18:28   ` Mark Salisbury
2001-09-20 19:12     ` Tom Rini
2001-09-20 22:22 ` Dan Malek
2001-09-21  5:45 ` Troy Benjegerdes
2001-09-28  6:37 ` Paul Mackerras
  -- strict thread matches above, loose matches on Subject: below --
2001-09-21  5:28 Albert D. Cahalan
2001-09-21  6:10 ` Dan Malek
2001-09-21 10:59   ` Ralph Blach
2001-09-21 18:48 Albert D. Cahalan
2001-09-22  0:22 ` Timothy A. Seufert
2001-09-22 20:06   ` Albert D. Cahalan
2001-09-24 17:10   ` Mark Salisbury
2001-09-22 14:23 ` Holger Bettag
2001-09-22 20:26   ` 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=3BAA4F46.1020002@mc.com \
    --to=mbs@mc.com \
    --cc=hobold@Informatik.Uni-Bremen.DE \
    --cc=linuxppc-dev@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 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.