From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] ARM926ejs: Add routines to invalidate D-Cache
Date: Fri, 12 Aug 2011 11:57:08 +0200 [thread overview]
Message-ID: <4E44F8F4.7030901@aribaud.net> (raw)
In-Reply-To: <201108110930.46500.marek.vasut@gmail.com>
On 11/08/2011 09:30, Marek Vasut wrote:
> That's actually not a bad idea, but we need to be definitelly 100% sure it'll
> work for all these different v5 and v6 cores !
That's what I'm afraid of: not all v5 or v6 cores may have the same set
of cache functions. I'll have a look at various ARMv5 based cores to get
a feel of the risk.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-08-12 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 2:49 [U-Boot] [PATCH v4] ARM926ejs: Add routines to invalidate D-Cache Hong Xu
2011-08-10 5:52 ` Marek Vasut
2011-08-10 5:56 ` Heiko Schocher
2011-08-10 6:17 ` Hong Xu
2011-08-10 6:36 ` Albert ARIBAUD
2011-08-10 6:41 ` Hong Xu
2011-08-10 7:13 ` Marek Vasut
2011-08-11 7:02 ` Aneesh V
2011-08-11 7:30 ` Marek Vasut
2011-08-12 9:57 ` Albert ARIBAUD [this message]
2011-08-12 10:04 ` Marek Vasut
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=4E44F8F4.7030901@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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