From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm_cortexa8: support cache flush to other soc
Date: Mon, 07 Sep 2009 19:47:02 -0500 [thread overview]
Message-ID: <4AA5A986.8060003@windriver.com> (raw)
In-Reply-To: <1f3430fb0909071706j52d843c5y69fce581b9e7fb7@mail.gmail.com>
Minkyu Kang wrote:
> Dear Dirk,
>
>
<snip>
I have lost track of this thread.
When last I worked this, it seemed like the cache routines were going to
be split.
1. generic cache routines
2. legacy soc cache routines.
Are the generic cache routines in place and can you use them?
Else can you handle your soc specific cache routines as part of a
legacy cache routine ?
The omap cache routines are dependent on omap rom code and fitting
new routines in using the omap specifics may not be the best way to
go.
Tom
>
> Thanks :)
> Minkyu Kang
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2009-09-08 0:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 8:26 [U-Boot] [PATCH] arm_cortexa8: support cache flush to other soc Minkyu Kang
2009-09-04 8:43 ` Dirk Behme
2009-09-04 9:34 ` Kyungmin Park
2009-09-04 10:45 ` Dirk Behme
2009-09-04 10:54 ` Kyungmin Park
2009-09-04 11:43 ` Dirk Behme
2009-09-04 14:29 ` Minkyu Kang
2009-09-04 15:06 ` Dirk Behme
2009-09-07 1:31 ` Minkyu Kang
2009-09-07 16:52 ` Dirk Behme
2009-09-08 0:06 ` Minkyu Kang
2009-09-08 0:47 ` Tom [this message]
2009-09-08 18:51 ` Dirk Behme
2009-09-08 22:23 ` Tom
2009-09-09 5:34 ` Minkyu Kang
2009-09-09 11:24 ` Tom
2009-09-09 12:04 ` Minkyu Kang
2009-09-10 19:02 ` Tom
2009-09-10 19:36 ` Paulraj, Sandeep
2009-09-04 22:24 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-04 11:06 ` Wolfgang Denk
2009-09-04 11:11 ` Kyungmin Park
2009-09-04 11:48 ` Wolfgang Denk
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=4AA5A986.8060003@windriver.com \
--to=tom.rix@windriver.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