From: Matt Porter <mporter@kernel.crashing.org>
To: "Jenkins, Clive" <Clive.Jenkins@xerox.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Yosemite/440EP why are readl()/ioread32() setuptoreadlittle-endian?
Date: Thu, 2 Feb 2006 07:39:40 -0700 [thread overview]
Message-ID: <20060202073940.C27740@cox.net> (raw)
In-Reply-To: <35786B99AB3FDC45A8215724617919736D921E@gbrwgceumf01.eu.xerox.net>; from Clive.Jenkins@xerox.com on Thu, Feb 02, 2006 at 11:26:22AM -0000
On Thu, Feb 02, 2006 at 11:26:22AM -0000, Jenkins, Clive wrote:
> I'm not sure all this fuss is justified in response to:
>
> > What is the preferred way of accessing non-PCI devices then?
> > Direct pointer access?
> > Bye, Peter Korsgaard
>
> Regardless of what standards or hardware might exist, I would be
> happy if Linux provided alternatives to readl()... that converted
> between big-endian and cpu-endian, so that I could write in my
> driver, for example:
As I pointed out, there are such alternatives. The iomap interface
provides what you need.
-Matt
next prev parent reply other threads:[~2006-02-02 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 11:26 Yosemite/440EP why are readl()/ioread32() setuptoreadlittle-endian? Jenkins, Clive
2006-02-02 14:39 ` Matt Porter [this message]
2006-02-02 17:16 ` Eugene Surovegin
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=20060202073940.C27740@cox.net \
--to=mporter@kernel.crashing.org \
--cc=Clive.Jenkins@xerox.com \
--cc=linuxppc-embedded@ozlabs.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.