linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: david.yangshuai@gmail.com (David Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: Problem with dma_alloc_coherent at linux-2.6.33-arm1 , with RealView platform,board PBX-A9 and armv7 instructions.
Date: Thu, 15 Jul 2010 19:16:24 +0800	[thread overview]
Message-ID: <AANLkTilyVdWrsrDy8tk9_vAxya8o5MSeKJJLEpxjDlSQ@mail.gmail.com> (raw)
In-Reply-To: <20100715100938.GH26212@n2100.arm.linux.org.uk>

patch-6220/1   can't be  patched on kernel version linux-2.6.33-arm1.

the file arch/arm/mm/cache-l2x0.c  may be too old for the patch.


On Thu, Jul 15, 2010 at 6:09 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Thu, Jul 15, 2010 at 03:34:58PM +0530, Shilimkar, Santosh wrote:
>> > -----Original Message-----
>> > From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-arm-
>> > kernel-bounces at lists.infradead.org] On Behalf Of David Yang
>> > Sent: Thursday, July 15, 2010 3:27 PM
>> > To: Russell King - ARM Linux
>> > Cc: linux-arm-kernel at lists.infradead.org; Ben Dooks
>> > Subject: Re: Problem with dma_alloc_coherent at linux-2.6.33-arm1 , with
>> > RealView platform,board PBX-A9 and armv7 instructions.
>> >
>> > I have explicitly added the barrier() in my driver, but it did't work.
>> >
>> > I will go on testing until solve the problem. I need more advice.
>> >
>> The 'barrier()' is just a compiler barrier. You should be using "mb" "rmb"
>> or "wmb" ?depending on the usage.
>
> It'd be useful if the patches which are destined for mainline get some
> independent testing by people who have experienced the problem, rather
> than creating their own solutions.
>
> We can then have much more confidence in the patch which may eventually
> be applied is solving problems people are seeing - and more importantly
> identify any defficiencies in the patch so we don't have to repeatedly
> patch the same area multiple times.
>

  reply	other threads:[~2010-07-15 11:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15  9:13 Problem with dma_alloc_coherent at linux-2.6.33-arm1 , with RealView platform,board PBX-A9 and armv7 instructions David Yang
2010-07-15  9:31 ` Ben Dooks
2010-07-15  9:38   ` Russell King - ARM Linux
2010-07-15  9:56     ` David Yang
2010-07-15  9:59       ` Russell King - ARM Linux
2010-07-15 10:06         ` David Yang
2010-07-15 10:04       ` Shilimkar, Santosh
2010-07-15 10:09         ` Russell King - ARM Linux
2010-07-15 11:16           ` David Yang [this message]
2010-07-15 11:28             ` Russell King - ARM Linux
2010-07-15 12:15           ` Problem with dma_alloc_coherent at linux-2.6.33-arm1 , withRealView " Catalin Marinas
2010-07-15  9:40   ` Problem with dma_alloc_coherent at linux-2.6.33-arm1 , with RealView " David Yang
2010-07-15 12:19   ` Problem with dma_alloc_coherent at linux-2.6.33-arm1 , withRealView " Catalin Marinas
2010-07-15  9:35 ` Problem with dma_alloc_coherent at linux-2.6.33-arm1 , with RealView " Russell King - ARM Linux
2010-07-15 12:21   ` Problem with dma_alloc_coherent at linux-2.6.33-arm1 , withRealView " Catalin Marinas
2010-07-15 12:52     ` David Yang
2010-07-15 12:56       ` Catalin Marinas
2010-07-15 13:10         ` David Yang
2010-07-15 13:17           ` Catalin Marinas
2010-07-17  7:05             ` David Yang
2010-07-19 12:29               ` Catalin Marinas
2010-07-20  3:17                 ` David Yang
2010-07-20  8:53                   ` Catalin Marinas
2010-07-20  9:22                     ` David Yang
2010-07-20  9:26                       ` Catalin Marinas
2010-07-15 12:25 ` Problem with dma_alloc_coherent at linux-2.6.33-arm1 , with RealView " Catalin Marinas
2010-07-15 12:57   ` David Yang

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=AANLkTilyVdWrsrDy8tk9_vAxya8o5MSeKJJLEpxjDlSQ@mail.gmail.com \
    --to=david.yangshuai@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).