From: Lee Revell <rlrevell@joe-job.com>
To: Phil.Nitschke@avalon.com.au
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: DMA buffer synchronisation with ioremap()
Date: Tue, 01 Aug 2006 15:51:15 -0400 [thread overview]
Message-ID: <1154461876.14540.70.camel@mindpipe> (raw)
In-Reply-To: <1154351427.3203.59.camel@toby.int.avalon.com.au>
On Mon, 2006-07-31 at 22:40 +0930, Phil Nitschke wrote:
> (I go no replies last week, so I'll try again, with less explanation...)
>
> If I master a DMA from a PCI device into a main memory buffer allocated
> with dma_alloc_noncoherent(), I need to synchronise the destination
> buffer using dma_sync_single_range_for_xxx() before and after the DMA.
>
> But if the buffer is a very large chunk of memory (reserved at boot
> time) which has been ioremap()-ed into the virtual address space, do I
> need to still synchronise that memory?
Maybe it's a better question for the linux-kernel list?
Lee
prev parent reply other threads:[~2006-08-01 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 13:10 DMA buffer synchronisation with ioremap() Phil Nitschke
2006-08-01 19:51 ` Lee Revell [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=1154461876.14540.70.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Phil.Nitschke@avalon.com.au \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.