From: feng <cuifeng226@163.com>
To: linuxppc-embedded@ozlabs.org
Subject: pci based on mpc8250
Date: Wed, 2 May 2007 09:11:33 +0000 (UTC) [thread overview]
Message-ID: <loom.20070502T105747-533@post.gmane.org> (raw)
hi all:
I have been working on my pci for about 2 mounths ,but I can't work it out.
I list the problems I encounter here.Any suggestion will be welcome.
We want to send 208 bytes per frame.but it was send in several frames.
We try to disalbe the snoop bit in our program ,choose another dma band
width.the result it we can speed up the speed ,but it can't be checked
through by our check program.what confused us is that the data gets by our
software transferes through the hardware is right .
some one suggests that:
When snooping is not used and a memeory region is cacheable, you should
invalidate cache area (executing as much DCBI instructions as required)
corresponding to the transfer region after each transfer before read it by the
core. Refer to the Programming Environments Manual for 32-Bit Implementations
of the PowerPC Architecture, Chapter 8 Instruction Set, dcbi.
our Latency Timer Register value is 0xc4,and the cachline is 0x8
thank you for you attention.
feng
reply other threads:[~2007-05-03 13:20 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=loom.20070502T105747-533@post.gmane.org \
--to=cuifeng226@163.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