From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Tue, 19 Mar 2013 18:32:39 -0500
Subject: [U-Boot] [RFC] command/cache: Add flush_cache command
In-Reply-To: <5148E1A5.4030502@freescale.com> (from yorksun@freescale.com on
	Tue Mar 19 17:07:33 2013)
References: <1363724992-9803-1-git-send-email-yorksun@freescale.com>
	<20130319230141.72357073@lilith> <5148E1A5.4030502@freescale.com>
Message-ID: <1363735959.16671.38@snotra>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 03/19/2013 05:07:33 PM, York Sun wrote:
> On 03/19/2013 03:01 PM, Albert ARIBAUD wrote:
> > What's the point of this command exactly? I can see the point of  
> range
> > flushes (and invalidates) in the code for drivers that use DMA, but  
> as a
> > shell command, I fail to see the interest of it.
> >
> 
> I am actually expecting this question. We have a situation that an
> application is copied by u-boot to its destination in memory. The code
> needs to be "seen" in the main memory. Without flushing cache, it is
> only visible to cores.

It's the same purpose as the cache flushing that happens in bootm,  
except for code loading that happens outside bootm.

-Scott