linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Callebaut Benoit <callebaut@mailandnews.com>
To: rowejames@acmsystems.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: PCI DMA support on the MPC8250
Date: Wed, 25 Jun 2003 03:01:08 -0400	[thread overview]
Message-ID: <3EFFFCC6@mailandnews.com> (raw)


Hello Jim,
I am working on a MPC8245, and I had the same problem. There is no support in
Linux for CPU initiated DMA. The pci_consistent_alloc functions and all others
related to DMA like pci_sync_single have nothing to do with DMA. Their only
job is to keep a block of memory synchronized with the cache or disable the
use of cache with it.
But the DMA transfers are working and are 5 time faster. You must only program
them. It is just 5 registers to configure. You buffers in RAM must be
allocated with consistent_alloc to avoid caching on them and you must always
write physical addresses in the DMA registers( use virt_to_phys).
Note For  PCI addresses virt_to_phys doesn't work well. You must take the
addresses from the "remap" function code. I did it and it works very well.

A good advice : Try to reduce the setup code for the DMA to a maximum.
Otherwise you won't gain anything for small blocks (setup time > memcpy time
).

Or if you Firewire chip support DMA use the DMA ability of your Firewire chip.

Good luck


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-06-25  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25  7:01 Callebaut Benoit [this message]
2003-06-25 13:17 ` PCI DMA support on the MPC8250 Allen Curtis
  -- strict thread matches above, loose matches on Subject: below --
2003-06-25 14:24 Callebaut Benoit
2003-06-24 18:22 Jim Rowe

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=3EFFFCC6@mailandnews.com \
    --to=callebaut@mailandnews.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rowejames@acmsystems.com \
    /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).