From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] cfi_flash.c and lost volatile qualifier
Date: Wed, 30 Apr 2008 11:51:48 -0400 [thread overview]
Message-ID: <48189594.30004@ge.com> (raw)
In-Reply-To: <20080430153830.3CC7024681@gemini.denx.de>
Wolfgang Denk wrote:
> In message <48188584.3060109@ge.com> you wrote:
>> The solution in the PowerPC world is to add a "eieio" or "sync"
>> instruction[1] appropriately[2], which prevents the bus interface unit
>> from reordering the memory operations.
>
> No, the solution for ALL architectures is to use the appropriate
> accessor macros which take care of such things (and probably contain
> calls like sync or similar).
>
> Best regards,
>
> Wolfgang Denk
Agreed.
If my theory is correct, Adrian has turned up a problem with the ARM
configuration that apparently only shows up for the PXA250. Or I'm
blowing smoke - nothing to see, move along.
The hairs on the back of my neck say it is a sync/bus interface unit
problem.
I don't know if it is significant, not being very intimately familiar
with ARM (and, in particular, the PXA250), but my quick grep turns up
./include/asm-arm/io.h and a quick browsing shows no syncs. The hairs
on the back of my neck are starting to ache. ;-)
static inline void sync(void)
{
}
#define __arch_getb(a) (*(volatile unsigned char *)(a))
gvb
next prev parent reply other threads:[~2008-04-30 15:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 14:32 [U-Boot-Users] drivers MMCplus for at91sam9x Pierre Savary
2008-04-09 17:49 ` Jean-Christophe PLAGNIOL-VILLARD
2008-04-10 10:32 ` Pierre Savary
2008-04-10 22:31 ` Ken.Fuchs at bench.com
2008-04-11 8:26 ` Pierre Savary
2008-04-11 15:48 ` Pierre Ossman
2008-04-11 18:54 ` Ken.Fuchs at bench.com
2008-04-12 9:28 ` Pierre Ossman
2008-04-15 10:18 ` Pierre Savary
2008-04-15 16:51 ` Ken.Fuchs at bench.com
[not found] ` <-6021840981243159212@unknownmsgid>
2008-04-15 19:25 ` Andy Fleming
2008-04-16 8:55 ` Pierre Savary
2008-04-16 23:30 ` Ken.Fuchs at bench.com
2008-04-22 11:55 ` Pierre Savary
2008-04-22 15:07 ` [U-Boot-Users] [PATCH] Add eSDHC driver Andy Fleming
2008-04-22 16:53 ` Anton Vorontsov
2008-04-23 19:23 ` Ken.Fuchs at bench.com
2008-04-24 6:24 ` Pierre Savary
2008-04-29 19:45 ` [U-Boot-Users] drivers MMCplus for at91sam9x Ken.Fuchs at bench.com
2008-04-29 20:20 ` [U-Boot-Users] cfi_flash.c and lost volatile qualifier Adrian Filipi
2008-04-29 20:43 ` Wolfgang Denk
2008-04-29 21:10 ` Adrian Filipi
2008-04-29 21:16 ` Jerry Van Baren
[not found] ` <alpine.DEB.1.10.0804300949360.13610@pmy.adscville>
2008-04-30 14:43 ` Jerry Van Baren
2008-04-30 15:11 ` Joakim Tjernlund
2008-04-30 15:21 ` Scott Wood
2008-04-30 15:34 ` Joakim Tjernlund
2008-04-30 15:41 ` Wolfgang Denk
2008-04-30 16:02 ` Scott Wood
2008-04-30 16:11 ` Joakim Tjernlund
2008-04-30 15:35 ` [U-Boot-Users] PPC sync/eieio (was cfi_flash.c and lost volatile qualifier) Jerry Van Baren
2008-04-30 15:38 ` [U-Boot-Users] cfi_flash.c and lost volatile qualifier Wolfgang Denk
2008-04-30 15:51 ` Jerry Van Baren [this message]
2008-05-08 11:17 ` Haavard Skinnemoen
2008-05-08 14:05 ` Adrian Filipi
2008-05-08 16:27 ` Haavard Skinnemoen
2008-04-30 14:20 ` [U-Boot-Users] drivers MMCplus for at91sam9x Pierre Savary
2008-04-30 16:25 ` Ken.Fuchs at bench.com
2008-04-30 20:31 ` Ken.Fuchs at bench.com
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=48189594.30004@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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.