From: Ron Bianco <ronb@lcsaudio.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Has anyone made the 8240 do burst reads from PCI memory?
Date: Fri, 06 Jun 2003 12:50:20 -0700 [thread overview]
Message-ID: <000401c32c64$dc6a4690$4d00a8c0@warp-speed> (raw)
Hello,
We have a custom 8240 board running a linux 2.2.x kernel variant with some dual
port SRAM mapped into PCI memory space using a custom CPLD. We use a modified
version of the sandpoint setup in the ppc linux kernel initialization code.
In the ISR of a custom device driver we read and write to the PCI mem
successfully.
FYI, although not a PCI expert, I'm trying to determine if we need to upgrade
our CPLD code in order to successfully support memory read cycles with more than
one data phase.
Even with sequential reads in groups of 8 words, ( or writes for that matter )
we are unable to get the 8240 to do other than single (beat) word read PCI
cycles. One 'strange' thing in particular is that the 8240 as PCI initiator is
keeping !FRAME asserted only very briefly.
It also de-asserts !IRDY very soon after the first data phase completes. It may
be that the 8240 is just indicating a wait and we need to handle that better.
Anyway, according to the 8240 user's manual it supports burst ordering of the
linear incrementing type for memory accesses when the 2 low order bits of the
address are 0, as we are doing.
So I was just wondering if anyone has actually gotten an 8240 to access PCI
memory with multiple beat, memory read cmds.?
regards, Ron
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-06-06 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 19:50 Ron Bianco [this message]
2003-06-09 20:35 ` Has anyone made the 8240 do burst reads from PCI memory? Jochen Roth
2003-06-09 22:53 ` Ron Bianco
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 6:57 Callebaut Benoit
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='000401c32c64$dc6a4690$4d00a8c0@warp-speed' \
--to=ronb@lcsaudio.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).