From: "Jonathan Qiang" <jqiang@haliplex.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: IDMA IN MPC82XX (i.e mpc8272)
Date: Wed, 8 Nov 2006 13:04:39 +1100 [thread overview]
Message-ID: <32A7B31E4005134E8BA805EBAAFB9DCD9C7A47@hellskitchen.haliplex.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
Any one who has any experience when using IDMA on mpc82xx?
Currently, the status what I have got is, memory-to-memory mode, both
Data bus had been set to 60x-bus, which means DDTB and SDTB are working
on 60x-bus. if set DMA_WRAP in DCM as 64-byte, SS_MAX,STS and DTS in
(IDMA Parameter RAM) all to 32 Bytes, there working good!
But if set DMA_WRAP more than 64-byte(i.e 256-bytes) ,SS_MAX,STS and DTS
in (IDMA Parameter RAM) all to 7*32 Bytes when WRAP = 256 . then got
some issues:
1. some bytes in a packet had been changed oddly. for example if some
bytes in the packet is "20 0f 17 2c...." after
IDMA transmission , the bytes will be changed as "20 1d 17 2c", there is
a slightly different with "17" and "1d".
2. some bytes had been swapped , for example "20 0f 17 2c" , after
transmission , the bytes in packet was "2c 17 0f 20".
Any ideas?
Is this the cache issue? I had enabled the snooping
[-- Attachment #2: Type: text/html, Size: 4837 bytes --]
reply other threads:[~2006-11-08 2:13 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=32A7B31E4005134E8BA805EBAAFB9DCD9C7A47@hellskitchen.haliplex.com.au \
--to=jqiang@haliplex.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