From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linux PPC Development <linuxppc-dev@ozlabs.org>, dwmw2@infradead.org
Subject: Re: [PATCH] powerpc/mpc52xx/mtd: fix mtd-ram access for 16-bit Local Plus Bus
Date: Sat, 13 Jun 2009 18:45:44 +0200 [thread overview]
Message-ID: <1244911551.3423.0@antares> (raw)
In-Reply-To: <fa686aa40906110927w60a5a74alaa3420b9bf3f3e44@mail.gmail.com> (from grant.likely@secretlab.ca on Thu Jun 11 18:27:53 2009)
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Am 11.06.09 18:27 schrieb(en) Grant Likely:
>> + *(u16 *)buf = *((volatile u16 *)(vdest - 1));
>> + buf[1] = *((u8 *)src);
>> + *((volatile u16 *)(vdest - 1)) = *(u16 *)buf;
>
> what is the purpose of volatile here? If you need io barriers, then
> use the in_/out_be16 macros.
Yes, you're right - should be completely superfluous here. A result of
copy & paste without thinking... :-(
> Blech. ugly #ifdef and not really multiplatform safe (yeah, I know
> it shouldn't break non-5200 platforms, but it does have an
> undesirable impact). There's got to be a better way.
Ouch, yes - I completely forgot the possibility of multi-platform
builds.
Am 11.06.09 19:28 schrieb(en) Grant Likely:
> So; the solution to me seems to be on an MPC5200 platform replace the
> offending hooks with MPC5200 specific variants at runtime.
Will re-work the patch that way! BTW, a dumb question: what is the
proper way to determine which cpu the system is running on? Check the
CPU node of the of tree?
Thanks, Albrecht.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-06-13 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:46 [PATCH] powerpc/mpc52xx/mtd: fix mtd-ram access for 16-bit Local Plus Bus Albrecht Dreß
2009-06-11 16:27 ` Grant Likely
2009-06-11 16:55 ` Wolfram Sang
2009-06-11 17:28 ` Grant Likely
2009-06-13 16:45 ` Albrecht Dreß [this message]
2009-06-13 17:09 ` Grant Likely
2009-09-04 8:51 ` David Woodhouse
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=1244911551.3423.0@antares \
--to=albrecht.dress@arcor.de \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--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).