linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Timothy A. Seufert" <tas@mindspring.com>,
	Mark Salisbury <mbs@mc.com>,
	Holger Bettag <hobold@Informatik.Uni-Bremen.DE>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ppc LE questions (seeking help hand info pointers)
Date: Fri, 21 Sep 2001 04:19:06 -0400	[thread overview]
Message-ID: <3BAAF7F9.B4DAB4BA@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0109210950130.3006-100000@mullein.sonytel.be


Geert Uytterhoeven wrote:

> AFAIK they do, for PCI accesses.

They do the same thing we do.  The ULTRASparc has address modifiers on the
load/store instructions to do byte swapping in the io macros, just like us.
The "other" Sparcs do it the hard way with actual byte swap code in the
macros.  There are comments in various files that clearly state Sparc is
big-endian without exception :-).


	-- Dan

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

  reply	other threads:[~2001-09-21  8: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
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 [this message]
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=3BAAF7F9.B4DAB4BA@mvista.com \
    --to=dan@mvista.com \
    --cc=geert@linux-m68k.org \
    --cc=hobold@Informatik.Uni-Bremen.DE \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mbs@mc.com \
    --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 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).