From: Kim Phillips Date: Wed, 18 Feb 2009 18:32:17 -0600 Subject: [U-Boot] Strange data behaviour In-Reply-To: <499BC47C.6060601@duran-audio.com> References: <499AA5B8.7030805@duran-audio.com> <20090217191211.5C469832E893@gemini.denx.de> <499BC47C.6060601@duran-audio.com> Message-ID: <20090218183217.1962dbb6.kim.phillips@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, 18 Feb 2009 09:19:08 +0100 Remco Poelstra wrote: > Wolfgang Denk schreef: > > I bet you are using a plain pointer access without a "volatile", > > which is essential here. Maybe even some form of "sync" is needed. In > > any case, you should use appropriate accessor functions to access > > device registers. > > I do not know any accessor functions. things like out_be32 (at least that's what it's called on ppc arch). > What do you mean with a "sync"? it's a processor instruction that ensures that memory and/or i/o accesses occur exactly when you specify they occur. For this reason, a sync instruction is included as a part of the accessor functions. Kim