From: Nick Barendt <nbarendt@vxitech.com>
To: linuxppc-dev@ozlabs.org
Subject: MPC5200 PCI TX/RX FIFO
Date: Thu, 10 Mar 2005 19:27:25 -0500 [thread overview]
Message-ID: <5.2.1.1.0.20050310185814.02b26630@mail.atiba.com> (raw)
Has anyone had luck getting the MPC5200 PCI RX or TX FIFOs
working, either directly or with Bestcomm DMA support? I've been trying to
do so for a few weeks, on and off, with little luck. I'm probably missing
something obvious.
I'm using Wolfgang's kernel tree, on a board similar to the IceCube.
I'd like to use the PCI RX FIFO to speed up moving data from a PCI
device - it looks like the RX FIFO is the most straight-forward mechanism
for bursting. I've had some luck getting the RX FIFO to pull data back
from a PCI device, and can get a peripheral interrupt from the RX FIFO, but
no matter what I do (read data from FIFO to DDR, clear status bits, etc.),
I can't seem to acknowledge the interrupt at the peripheral end, so it
continues to fire. I can't find anything in the MPC5200 user manual about
acknowledging the interrupt in the PCI controller, unlike the FEC, say,
which has documentation on how to ack FEC interrupts.
I then went the Bestcomm route, using the Bestcomm API, but I'm
clearly missing something there, because the DMA engine indicates a TEA
after a very long timeout. That problem might be related to my PCI RX FIFO
interrupt problem, or might be completely different. Might it be that the
Alarm signal to the DMA engine is the same as the interrupt signal to the core?
In the end, I'd like to go the DMA route. It is likely that using
the RX FIFO would be a significant improvement over what I have right now,
though, and it is (hopefully) easier to get up and running.
Does anyone have any wisdom (or, better yet, sample code :-) they
can share on this?
Nick Barendt
VXI Technology, Inc.
Cleveland Instruments Division
5425 Warner Road, Suite 13
Valley View, OH 44125
PH: 216-447-4059
FAX: 216-447-8951
nbarendt@vxitech.com
reply other threads:[~2005-03-11 0:50 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=5.2.1.1.0.20050310185814.02b26630@mail.atiba.com \
--to=nbarendt@vxitech.com \
--cc=linuxppc-dev@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