From: Peter Korsgaard <jacmet@sunsite.dk>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: "Jenkins, Clive" <Clive.Jenkins@xerox.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Yosemite/440EP why are readl()/ioread32() setup to readlittle-endian?
Date: Wed, 01 Feb 2006 22:14:15 +0100 [thread overview]
Message-ID: <87wtgeeq8o.fsf@48ers.dk> (raw)
In-Reply-To: <20060201104405.C16064@cox.net> (Matt Porter's message of "Wed, 1 Feb 2006 10:44:05 -0700")
>>>>> "Matt" == Matt Porter <mporter@kernel.crashing.org> writes:
Matt> read*/write* and ioread*/iowrite* generate outbound little
Matt> endian cycles on ALL arches, period. They are intended
Matt> only for PCI use and have generic names only because of
Matt> the assumption that "all the world is a PC".
What is the preferred way of accessing non-PCI devices then? Direct
pointer access?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2006-02-01 21:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 11:19 Yosemite/440EP why are readl()/ioread32() setup to readlittle-endian? Jenkins, Clive
2006-02-01 17:02 ` David Hawkins
2006-02-01 17:44 ` Matt Porter
2006-02-01 17:53 ` David Hawkins
2006-02-01 18:04 ` David Hawkins
2006-02-01 18:11 ` Eugene Surovegin
2006-02-01 18:20 ` David Hawkins
2006-02-01 18:23 ` Eugene Surovegin
2006-02-01 21:14 ` Peter Korsgaard [this message]
2006-02-02 0:54 ` Kumar Gala
2006-02-02 3:07 ` Matt Porter
2006-02-02 8:09 ` Peter Korsgaard
2006-02-02 9:08 ` Eugene Surovegin
2006-02-02 17:34 ` Dale Farnsworth
2006-02-02 14:21 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2006-02-01 18:35 Jenkins, Clive
2006-02-01 20:35 ` David Hawkins
2006-02-02 9:35 Jenkins, Clive
2006-02-02 9:46 ` Eugene Surovegin
2006-02-02 14:37 ` Matt Porter
2006-02-02 17:45 ` Eugene Surovegin
2006-02-02 18:16 ` Matt Porter
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=87wtgeeq8o.fsf@48ers.dk \
--to=jacmet@sunsite.dk \
--cc=Clive.Jenkins@xerox.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mporter@kernel.crashing.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).