public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3 v3] ARM: ARM926EJS - Add cache operations
Date: Mon, 05 Sep 2011 21:45:35 +0200	[thread overview]
Message-ID: <4E6526DF.1010609@aribaud.net> (raw)
In-Reply-To: <201109021357.53889.marek.vasut@gmail.com>

Le 02/09/2011 13:57, Marek Vasut a ?crit :
> On Friday, September 02, 2011 01:43:39 PM Simon Guinot wrote:
>> On Fri, Sep 02, 2011 at 12:23:54PM +0200, Marek Vasut wrote:
>>> On Friday, September 02, 2011 12:22:05 PM Simon Guinot wrote:
>>>> Hi Hong,
>>>>
>>>> On Mon, Aug 15, 2011 at 03:08:51PM +0800, Hong Xu wrote:
>>>>> Hi Marek,
>>>>>
>>>>> On 08/11/2011 12:47 PM, Marek Vasut wrote:
>>>>>> On Thursday, August 11, 2011 05:27:37 AM Hong Xu wrote:
>>>>>>> Add a new file arch/arm/cpu/arm926ejs/cache.c and put cache
>>>>>>> operations into this file.
>>>>>>>
>>>>>>> Signed-off-by: Hong Xu<hong.xu@atmel.com>
>>>>>>> ---
>>>>>>>
>>>>>>> V2:
>>>>>>> 	Fixed a typo when CONFIG_SYS_DCACHE_OFF is defined
>>>>>>>
>>>>>>> V3:
>>>>>>> 	Undo changes in include/configs/at91sam9260ek.h
>>>>>>> 	It's for testing purpose
>>>>>>> 	
>>>>>>>    arch/arm/cpu/arm926ejs/Makefile |    2 +-
>>>>>>>    arch/arm/cpu/arm926ejs/cache.c  |  142
>>>>>>>
>>>>>>> +++++++++++++++++++++++++++++++++++++++ 2 files changed, 143
>>>>>>> insertions(+), 1 deletions(-)
>>>>>>>
>>>>>>>    create mode 100644 arch/arm/cpu/arm926ejs/cache.c
>>>>
>>>> What is the status for this patch ?
>>>>
>>>> I have failed to find any trace for this patch in patchwork or in the
>>>> arm git repository...
>>>
>>> We discussed this should be moved to arch/arm/cpu/armv5 (Aneesh V's idea
>>> ... I dunno what's this guys' full name ;-D). I tested this patch on
>>> certain type of CPU and it works really good. I'd be really glad if we
>>> got this mainline!
>>
>> Yes. Moreover some drivers (as mvgbe) really needs such functions to fix
>> the DMA operations when D-cache is enabled.
>
> I have some fixes already queued, yes.
>
>>
>> Simon

Hi folks,

I'm trying to locate the latest version of this set's patches in 
patchwork and I can't find them at all in any state. What am I missing?

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-09-05 19:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11  3:27 [U-Boot] [PATCH 3/3 v3] ARM: ARM926EJS - Add cache operations Hong Xu
2011-08-11  4:47 ` Marek Vasut
2011-08-15  7:08   ` Hong Xu
2011-09-02 10:22     ` Simon Guinot
2011-09-02 10:23       ` Marek Vasut
2011-09-02 11:43         ` Simon Guinot
2011-09-02 11:57           ` Marek Vasut
2011-09-05 19:45             ` Albert ARIBAUD [this message]
2011-09-05 19:50               ` Marek Vasut
2011-09-06  6:19                 ` Albert ARIBAUD
2011-09-06  6:40                   ` Marek Vasut
2011-09-06 11:38                     ` Albert ARIBAUD
2011-09-06 14:21                       ` Marek Vasut
2011-09-06 11:43                     ` [U-Boot] [RFC] Long term ARM ISA/cpu/core code organization (was: [PATCH 3/3 v3] ARM: ARM926EJS - Add cache operations) Albert ARIBAUD
2011-09-06 14:21                       ` Marek Vasut
2011-09-07 14:02                       ` [U-Boot] [RFC] Long term ARM ISA/cpu/core code organization Aneesh V

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=4E6526DF.1010609@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