From: Callebaut Benoit <callebaut@mailandnews.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: DMA & cache coherency on 8245
Date: Fri, 9 May 2003 08:15:35 -0400 [thread overview]
Message-ID: <3EBF1042@mailandnews.com> (raw)
I,
I have written DMA functions to do software initiateds DMA transfers on the
8245. But I have some problem with cache I think.
I allocated the buffers for DMA, configure the DMA (I use no snooping) and
launch it.
There is only part of the data that are transfered when doing mem-mem dmas or
nothing at all when doing mem-pci transfers.
I tried to use invalidate_dcache_range on the block (allocated with
__get_free_pages ) but it crashed (Exception 0X300 (memory access)).
How can I be sure of the coherency of the cache ?
Thanks,
Benoit Callebaut
------------------------------------------------------------
Get your FREE web-based e-mail and newsgroup access at:
http://MailAndNews.com
Create a new mailbox, or access your existing IMAP4 or
POP3 mailbox from anywhere with just a web browser.
------------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-05-09 12:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EBF1042@mailandnews.com \
--to=callebaut@mailandnews.com \
--cc=linuxppc-embedded@lists.linuxppc.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).