From: Pedro Parrilla <pparrilla@prodys.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Rx problems with IDMA on MPC860...
Date: Thu, 08 May 2003 09:47:58 +0200 [thread overview]
Message-ID: <3EBA0BAE.93167851@prodys.net> (raw)
Hi,
I'm working on a MPC860T. I've been trying to receive from a
peripheral via IDMA and it seems to work OK, but when I study data
received from IDMA I can see that there are some bytes at the end of
each IDMA buffer received that are wrong, in fact they haven't been
written to the buffer and previous bytes remain; but interrupts are
received Ok, and the number of read bytes in the peripheral are the IDMA
set.
It could be an access problem to the peripheral with IDMA(without
IDMA this access is totally OK!).
Does anybody have any experience in this regard?
Thank you in advance.
---------------------------------------------
Pedro Parrilla Jimena Prodys.S.L
Embedded Systems Programming Trigo,54
e-mail pparrilla@prodys.net Leganes(Madrid) 28914
Tel.:+34916896880 http://www.prodys.net
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-05-08 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 7:47 Pedro Parrilla [this message]
2003-05-08 9:34 ` Rx problems with IDMA on MPC860 Wolfgang Denk
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=3EBA0BAE.93167851@prodys.net \
--to=pparrilla@prodys.net \
--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).