From: Peter Graf <p.graf@itknet.de>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] CS8900: Tx interrupt lost
Date: Tue, 14 Aug 2001 04:59:00 -0000 [thread overview]
Message-ID: <3.0.5.32.20010814135005.00905e90@192.168.128.220> (raw)
Trenton D. Adams wrote:
>What does that mean exactly? Maybe 250ms isn't long enough for a
>transmit?
>
>CS8900: Tx interrupt lost
Don't know about your target. Mine is a custom Hitachi SH3.
I had the same problem, if I just rely in Interrupts for Transmission.
On my target, the problem would not disappear if I send shorter packets or
use a longer timeout.
It seems that the interupts are really lost, either due to a hardware problem
of the Cirrus logic chip, or unlucky programming of its registers.
I worked around the problem by polling the device in addition to using the
interrupt.
Peter
next reply other threads:[~2001-08-14 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 4:59 Peter Graf [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 9:39 Todd Malsbary
2001-08-14 9:56 ` Jonathan Larmour
2001-08-14 13:09 ` Trenton D. Adams
2001-08-10 12:50 Trenton D. Adams
2001-08-13 11:37 ` Trenton D. Adams
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=3.0.5.32.20010814135005.00905e90@192.168.128.220 \
--to=p.graf@itknet.de \
--cc=ecos-discuss@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).