From: Adrian Cox <adrian@humboldt.co.uk>
To: Oliver Korpilla <okorpil@fh-landshut.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC7455 DMA buffer strangeness
Date: Tue, 06 Jul 2004 10:34:12 +0100 [thread overview]
Message-ID: <1089106451.937.85.camel@localhost> (raw)
In-Reply-To: <40EA6739.2040408@fh-landshut.de>
On Tue, 2004-07-06 at 09:47, Oliver Korpilla wrote:
> The buffer is not written to in kernel space, but in user space. An ioctl() is
> made for triggering the DMA. The user space mapping will lead to direct writes
> to that physical buffer address, so the DMA engine of my PCI-VME-bridge chip
> should see only what I wrote in user space, regardless of the kernel mapping.
> (But it doesn't in reality!)
It's certainly possible that part of the page has ended up in cache.
Why are you trying to turn off cache coherency? This should all work if
your userspace mapping is cache coherent.
- Adrian Cox
Humboldt Solutions Ltd.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-06 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 8:31 MPC7455 DMA buffer strangeness Oliver Korpilla
2004-07-06 8:34 ` Adrian Cox
2004-07-06 8:47 ` Oliver Korpilla
2004-07-06 9:34 ` Adrian Cox [this message]
2004-07-06 9:46 ` Oliver Korpilla
2004-07-06 10:09 ` Oliver Korpilla
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=1089106451.937.85.camel@localhost \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=okorpil@fh-landshut.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;
as well as URLs for NNTP newsgroup(s).