From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arthur Othieno <a.othieno@bluewin.ch>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc32: Big-endian I/O memory accessors.
Date: Mon, 22 Aug 2005 07:22:41 +1000 [thread overview]
Message-ID: <1124659361.5197.121.camel@gaston> (raw)
In-Reply-To: <20050821011649.GA31839@mars>
On Sat, 2005-08-20 at 21:16 -0400, Arthur Othieno wrote:
> I/O memory accessors. Big-endian version. For those busses/devices
> that do export big-endian I/O memory.
>
> Of notable relevance/reference:
>
> http://lwn.net/Articles/132804/
> http://ozlabs.org/pipermail/linuxppc-embedded/2005-August/019798.html
> http://ozlabs.org/pipermail/linuxppc-embedded/2005-August/019752.html
>
> Signed-Off-By: Arthur Othieno <a.othieno@bluewin.ch>
>
No, that's not correct. You need to use the in_be/out_be variants which
provide proper memory barriers.
Ben.
next prev parent reply other threads:[~2005-08-21 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 1:16 [PATCH] ppc32: Big-endian I/O memory accessors Arthur Othieno
2005-08-21 21:22 ` Benjamin Herrenschmidt [this message]
2005-08-22 12:51 ` Arthur Othieno
-- strict thread matches above, loose matches on Subject: below --
2005-10-10 21:50 Arthur Othieno
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=1124659361.5197.121.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=a.othieno@bluewin.ch \
--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 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.