From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Herrera-Bendezu, Luis" <lherrera@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] [Xenomai -help] User space access to DMA memory
Date: Wed, 12 Jan 2011 23:15:39 +0100 [thread overview]
Message-ID: <4D2E280B.1060308@domain.hid> (raw)
In-Reply-To: <6FCCA913376DD7488F4139A4D11B8F4801674280@domain.hid>
Herrera-Bendezu, Luis wrote:
>
> I am using PPC405 processor which does not support snooping and yes
> CONFIG_NOT_COHERENT_CACHE is defined. But I still need to make memory
> consistent (dma_sync_single_*) after each DMA transfer.
That is because the memory is mapped cacheable in user-space. You need
the path which sets the vma protection to non-cacheable, but add an
rtdm_iomap_noncacheable_to_user function.
--
Gilles.
next prev parent reply other threads:[~2011-01-12 22:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 16:52 [Xenomai-help] [Xenomai -help] User space access to DMA memory Herrera-Bendezu, Luis
2011-01-01 22:44 ` Gilles Chanteperdrix
2011-01-05 21:03 ` Herrera-Bendezu, Luis
2011-01-05 21:33 ` Gilles Chanteperdrix
2011-01-05 22:07 ` Steven A. Falco
2011-01-05 22:29 ` Gilles Chanteperdrix
2011-01-06 13:48 ` Herrera-Bendezu, Luis
2011-01-06 13:55 ` Gilles Chanteperdrix
2011-01-11 23:27 ` Gilles Chanteperdrix
2011-01-12 13:14 ` Herrera-Bendezu, Luis
2011-01-12 13:35 ` Gilles Chanteperdrix
2011-01-12 16:03 ` Herrera-Bendezu, Luis
2011-01-12 16:26 ` Gilles Chanteperdrix
2011-01-12 18:16 ` Herrera-Bendezu, Luis
2011-01-12 20:20 ` Gilles Chanteperdrix
2011-01-12 20:36 ` Gilles Chanteperdrix
2011-01-12 21:57 ` Herrera-Bendezu, Luis
2011-01-12 22:11 ` Philippe Gerum
2011-01-12 22:14 ` Gilles Chanteperdrix
2011-01-12 22:18 ` Gilles Chanteperdrix
2011-01-12 22:45 ` Gilles Chanteperdrix
2011-01-13 8:27 ` Philippe Gerum
2011-01-13 8:33 ` Gilles Chanteperdrix
2011-01-12 22:15 ` Gilles Chanteperdrix [this message]
2011-01-06 14:32 ` Steven A. Falco
2011-01-06 14:44 ` Gilles Chanteperdrix
2011-01-06 14:45 ` Steven A. Falco
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=4D2E280B.1060308@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lherrera@domain.hid \
--cc=xenomai@xenomai.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.