From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] command/cache: Add flush_cache command
Date: Wed, 20 Mar 2013 11:44:31 -0500 [thread overview]
Message-ID: <1363797871.25034.1@snotra> (raw)
In-Reply-To: <20130320145104.03CB820063B@gemini.denx.de> (from wd@denx.de on Wed Mar 20 09:51:03 2013)
On 03/20/2013 09:51:03 AM, Wolfgang Denk wrote:
> Dear York Sun,
>
> In message <1363724992-9803-1-git-send-email-yorksun@freescale.com>
> you wrote:
> > When we need the copied code/data in the main memory, we can flush
> the
> > cache now. It uses the existing function flush_cache. Syntax is
> >
> > flush_cache <addr> <size>
> >
> > The addr and size are given in hexadecimal. Like memory command,
> there is
> > no sanity check for the parameters.
>
> Why would it be necessary to ever run this manually?
>
> I feel you are just papering over bugs / shortcomings elsewhere in the
> code. Should we not rather fix the places where the cache flushes are
> missing in the code?
Possibly -- the alternative would be to have every command that
modifies memory flush that region of cache afterward (cp, tftp, etc).
You could say the same thing about the existing cache command, though.
-Scott
next prev parent reply other threads:[~2013-03-20 16:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 20:29 [U-Boot] [RFC] command/cache: Add flush_cache command York Sun
2013-03-19 22:01 ` Albert ARIBAUD
2013-03-19 22:07 ` York Sun
2013-03-19 23:32 ` Scott Wood
2013-03-20 13:59 ` Albert ARIBAUD
2013-03-20 14:58 ` Wolfgang Denk
2013-03-20 16:43 ` Scott Wood
2013-03-20 17:38 ` Albert ARIBAUD
2013-03-20 18:16 ` Scott Wood
2013-03-20 19:15 ` Tom Rini
2013-03-20 19:36 ` Scott Wood
2013-03-20 19:59 ` Tom Rini
2013-03-20 21:31 ` Scott Wood
2013-03-21 5:42 ` Wolfgang Denk
2013-03-21 5:39 ` Wolfgang Denk
2013-03-21 12:29 ` Tom Rini
2013-03-21 13:37 ` Wolfgang Denk
2013-03-21 18:22 ` Scott Wood
2013-03-21 19:25 ` Wolfgang Denk
2013-03-21 20:34 ` Scott Wood
2013-03-22 6:30 ` Albert ARIBAUD
2013-03-22 12:17 ` Tom Rini
2013-03-22 14:03 ` Wolfgang Denk
2013-03-22 14:29 ` Tom Rini
2013-03-22 15:57 ` Albert ARIBAUD
2013-03-22 16:48 ` Scott Wood
2013-03-22 17:19 ` Tom Rini
2013-03-22 20:39 ` Wolfgang Denk
2013-03-20 22:11 ` Albert ARIBAUD
2013-03-20 22:35 ` Scott Wood
2013-03-20 23:33 ` Michael Cashwell
2013-03-20 23:48 ` Scott Wood
2013-03-21 0:27 ` Michael Cashwell
2013-03-21 0:31 ` Scott Wood
2013-03-21 5:02 ` Sricharan R
2013-03-21 18:51 ` Scott Wood
2013-03-21 17:58 ` Albert ARIBAUD
2013-03-21 18:07 ` Scott Wood
2013-03-21 19:21 ` Wolfgang Denk
2013-03-20 19:40 ` York Sun
2013-03-20 14:51 ` Wolfgang Denk
2013-03-20 16:44 ` Scott Wood [this message]
2013-04-03 14:02 ` Jim Chargin
2013-04-18 17:09 ` Scott Wood
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=1363797871.25034.1@snotra \
--to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox