From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] The cache flush using coprocessor must be in lib_arm/cache-cp15.c
Date: Fri, 29 May 2009 08:15:47 +0200 [thread overview]
Message-ID: <4A1F7D93.8010900@googlemail.com> (raw)
In-Reply-To: <20090528192836.GA1802@game.jcrosoft.org>
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:51 Thu 28 May , Kim, Heung Jun wrote:
>> Hi? I'm about to suggest one more thing related to "change cpu.c under
>> cpu/arm_cortexa8 dir to common code.".
>>
>> asm ("mcr p15, 0, %0, c7, c5, 0": :"r" (0));
>>
>> It's the common feature all over the arm core, not only arm cortex A8.
>> The common cache function is defined in the lib_arm/cache-cp15.c as you
>> know. So, It's seems the better method that cache_flush() is moved to
>> lib_arm/cache-cp15.c
> NACK
>
> to boot linux we are suppose to clean both cache I and DCache
>
> the I/DCache flush is armv and arch dependant (example ARM7TDMI, armv4wt, armv3,
> armv7, etc...)
>
> so for now please let it in cpu/$(ARCH)/cpu.c
Well, in
http://lists.denx.de/pipermail/u-boot/2009-May/053396.html
Kim mentioned that he shuffles around the code due to compile errors
while adding his new code. So we have to see if we can stay with the
current implementation or have to change something.
Kim: What compile errors do you get for cache_flush()? Could you check
if you really don't need it? Why don't you get compile errors if you
move it from cpu/arm_cortexa8/cpu.c to lib_arm/cache-cp15.c?
Best regards
Dirk
next prev parent reply other threads:[~2009-05-29 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 8:51 [U-Boot] [PATCH] The cache flush using coprocessor must be in lib_arm/cache-cp15.c Kim, Heung Jun
2009-05-28 15:01 ` Dirk Behme
2009-05-28 19:28 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-29 6:15 ` Dirk Behme [this message]
2009-05-29 6:44 ` Kim, Heung Jun
2009-05-29 7:07 ` Dirk Behme
2009-05-29 7:15 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-29 7:38 ` Dirk Behme
2009-05-29 9:24 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-29 9:48 ` Dirk Behme
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=4A1F7D93.8010900@googlemail.com \
--to=dirk.behme@googlemail.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