From: Brian Waite <bwaite@irobot.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: linux DMA capabilities in MV64460
Date: Tue, 20 Dec 2005 09:27:35 -0500 [thread overview]
Message-ID: <200512200927.35976.bwaite@irobot.com> (raw)
In-Reply-To: <20051220010136.GA31165@mag.az.mvista.com>
On Monday 19 December 2005 8:01 pm, Mark A. Greer wrote:
> >
> > up the mv64460. One source told me:
> > > In order to do PCI bursts, you'll need to use a DMA engine. The
> > > MV64460 does contain a DMA engine, but you'd need to write a driver
> > > to access it.
>
> That is not correct (assuming the quote is not out of context).
> The bridge supports bursting on the PCI bus as long as the bridge is
> configured correctly and the PCI device is making an appropriate request.
> Note, however, that there are many errata for the Marvell parts including
> some with cache coherency.
There are many many errata regarding cache coherency. Also, the PCI bandwidth
the bridge is capable of with coherency enabled is very small. You will most
likely need to use sw coherency for any real speed.
> If your system is running with coherency on,
> you may have to limit your bursts to 32 bytes (i.e., the size of one
> cache line).
You will have to limit your self to 32 byte bursts with coherency. This is a
requirement not an errata.
> > Is there a summary of what is possible and/or not possible with the 4
> > IDMA channels on the mv64460?
>
> The only real documentation is the bridge's user manual from Marvell.
> Unfortunately, you must sign an NDA to get access to it so I can't share
> mine with you. You will need access to that info to get very far so I
> recommend you contact the people in your company that can make that
> happen, ASAP.
Ask for the errata sheets while your at it. You WILL need them :)
You really do need the chipset docs to do anything intelligent with the IDMA
controllers.
Thanks
Brian
next prev parent reply other threads:[~2005-12-20 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kw3bkovcup.fsf@lamorak.int.avalon.com.au>
2005-12-20 1:01 ` linux DMA capabilities in MV64460 Mark A. Greer
2005-12-20 14:27 ` Brian Waite [this message]
2005-12-20 17:54 ` Mark A. Greer
2005-12-22 0:54 ` Phil Nitschke
2006-03-06 4:09 ` Phil Nitschke
2006-03-06 13:21 ` Brian Waite
2006-03-08 14:02 ` Phil Nitschke
2006-03-08 22:36 ` Adrian Cox
2006-03-09 8:02 ` Phil Nitschke
2005-12-22 2:59 KokHow Teh
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=200512200927.35976.bwaite@irobot.com \
--to=bwaite@irobot.com \
--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 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).