From: Michael Barkowski <michaelbarkowski@ruggedcom.com>
To: linuxppc-dev@ozlabs.org
Cc: Timur Tabi <timur@freescale.com>
Subject: Is volatile always verboten for FSL QE structures?
Date: Fri, 02 Oct 2009 10:14:48 -0400 [thread overview]
Message-ID: <4AC60AD8.8030509@ruggedcom.com> (raw)
Just wondering - is there a case where using volatile for UCC parameter RAM for example will not work, or is the use of I/O accessors everywhere an attempt to be portable to other architectures?
I'm asking because I really want to know ;)
--
Michael Barkowski
905-482-4577
next reply other threads:[~2009-10-02 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 14:14 Michael Barkowski [this message]
2009-10-02 14:46 ` Is volatile always verboten for FSL QE structures? Timur Tabi
2009-10-02 16:41 ` Kumar Gala
2009-10-02 16:57 ` Michael Barkowski
2009-10-02 18:08 ` Guillaume Knispel
2009-10-03 9:55 ` Simon Richter
2009-10-03 11:20 ` Benjamin Herrenschmidt
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=4AC60AD8.8030509@ruggedcom.com \
--to=michaelbarkowski@ruggedcom.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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).