From: Robin Farine <acnrf@dial.eunet.ch>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Moving serial processing into ISR..
Date: Tue, 13 Feb 2001 10:09:00 -0000 [thread overview]
Message-ID: <86hf1y1nde.fsf@halftrack.hq.acn-group.ch> (raw)
In-Reply-To: <Pine.LNX.4.21.0102131733450.23479-100000@platinum.limerick.sslinc.com>
"David Airlie" <David.Airlie@parthus.com> writes:
> Has anyone ever moved the serial processing for a driver from the DSR into
> the ISR, and if so has anyone got any examples of this, or a quick note on
> what not do to do while trying this ..
If you need this than I guess you have a dumb UART without FIFO and loose
characters at speeds higher than 9600 bps ... I had once to deal with such a
problem. My solution implemented a software FIFO (aka ring buffer) shared
between the ISR and the DSR; the ISR just took characters out of the UART data
register and added them to the ring (about 12 MIPS instructions) while the DSR
performed the rest of the work.
HTH
Robin
prev parent reply other threads:[~2001-02-13 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 8:18 David Airlie
2001-02-13 10:09 ` Robin Farine [this message]
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=86hf1y1nde.fsf@halftrack.hq.acn-group.ch \
--to=acnrf@dial.eunet.ch \
--cc=ecos-discuss@sources.redhat.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).