From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] move L2 cache enable/disable function to cache.c in the omap3 SoC directory
Date: Sun, 07 Jun 2009 14:24:27 +0200 [thread overview]
Message-ID: <4A2BB17B.8050406@googlemail.com> (raw)
In-Reply-To: <20090607120847.GG25032@game.jcrosoft.org>
Dear Jean-Christophe,
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 21:16 Tue 02 Jun , Kim, Heung Jun wrote:
>> CC: Dirk Behme <dirk.behme@googlemail.com>
>> Signed-off-by: HeungJun, Kim <riverful.kim@samsung.com>
>>
>> ---
>>
>> The omap3 L2 cache enable/disable function in the cpu/arm_cortexa8/cpu.c moved
>> to cpu/arm_cortexa8/omap3/cache.c. Because, it must be CortexA8 ARCH generic
>> code below the cpu/arm_cortexa8.
>>
>> This patches fixes the First issue in the following
>>
>> http://lists.denx.de/pipermail/u-boot/2009-May/053433.html
>>
>> The Second issue is fixed by
>>
>> http://lists.denx.de/pipermail/u-boot/2009-May/053490.html
>>
>> cpu/arm_cortexa8/cpu.c | 70 ++---------------------------
>> cpu/arm_cortexa8/omap3/Makefile | 2 +-
>> cpu/arm_cortexa8/omap3/board.c | 5 +-
>> cpu/arm_cortexa8/omap3/cache.c | 96 +++++++++++++++++++++++++++++++++++++++
>> include/asm-arm/cache.h | 31 +++++++++++++
>> 5 files changed, 135 insertions(+), 69 deletions(-)
>> create mode 100644 cpu/arm_cortexa8/omap3/cache.c
>> create mode 100644 include/asm-arm/cache.h
> applied to arm/next with manual merge
>
> for your next please do base your code on the arm/next
Yes, I noticed this, too.
Thanks for manual merge,
Dirk
prev parent reply other threads:[~2009-06-07 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 12:16 [U-Boot] [PATCH] move L2 cache enable/disable function to cache.c in the omap3 SoC directory Kim, Heung Jun
2009-06-07 12:08 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-07 12:24 ` Dirk Behme [this message]
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=4A2BB17B.8050406@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