From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PPC PCI bus registers
Date: Thu, 17 Sep 2009 09:11:28 -0700 [thread overview]
Message-ID: <4AB25FB0.2080007@embeddedarm.com> (raw)
In-Reply-To: <1253150651.8375.328.camel@pasglop>
Benjamin,
> ioremap + readN / writeN will give you fully ordered behaviour. It's
> only when you try to be sneaky or speedy and use the __raw variants
> that you have to be more careful.
You've been most helpful, thanks.
--
Best Regards,
________________________________________________________________
Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200
16525 East Laser Drive | fax: (480) 837-5300
Fountain Hills, AZ 85268 | web: www.embeddedARM.com
prev parent reply other threads:[~2009-09-17 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:44 PPC PCI bus registers Eddie Dawydiuk
2009-09-02 23:56 ` Grant Likely
2009-09-03 10:00 ` Benjamin Herrenschmidt
2009-09-16 18:58 ` Eddie Dawydiuk
2009-09-16 21:54 ` Benjamin Herrenschmidt
2009-09-16 22:11 ` Eddie Dawydiuk
2009-09-17 1:24 ` Benjamin Herrenschmidt
2009-09-17 16:11 ` Eddie Dawydiuk [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=4AB25FB0.2080007@embeddedarm.com \
--to=eddie@embeddedarm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@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 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).