From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Brad Parker <brad@parker.boston.ma.us>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: asm/io.h; why does writel() write an le32 on ppc?
Date: Tue, 06 Mar 2001 18:30:15 -0500 [thread overview]
Message-ID: <3AA57307.E6AA26FF@mandrakesoft.com> (raw)
In-Reply-To: 200103062315.SAA01659@p2.parker.boston.ma.us
Brad Parker wrote:
> Sorry to be daft, but why does writel() write an le32 on the ppc?
> (is PCI defined as little endian?)
Yes. But there is always __raw_{read,write}[bwl]. That is part of the
API too.
Caveat programmer, though: IIRC there are other differences besides
endian when using __raw_xxx. I think there might be a lack of flushing,
etc., too.
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-06 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 23:15 asm/io.h; why does writel() write an le32 on ppc? Brad Parker
2001-03-06 23:23 ` Gabriel Paubert
2001-03-06 23:28 ` Brad Parker
2001-03-07 1:15 ` Gabriel Paubert
2001-03-06 23:30 ` Jeff Garzik [this message]
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=3AA57307.E6AA26FF@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=brad@parker.boston.ma.us \
--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 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).