From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Uart missing chars when in Release
Date: Mon, 28 Jan 2008 20:40:00 -0000 [thread overview]
Message-ID: <fnl79n$16k$1@ger.gmane.org> (raw)
In-Reply-To: <fnku29$sm6$1@ger.gmane.org>
On 2008-01-28, Grant Edwards <grante@visi.com> wrote:
> The way I usually do that is to instrument all the DSRs so that
> they set a spare port pin high at entry and low at exit.
Though I usually just put instrumentation code into individual
DSR's, you could probably accomplish the same thing by adding
some code the the DSR dispatcher that sets/clears port pins
when dispatching DSRs. You could also do the same thing with
ISRs.
--
Grant Edwards grante Yow! TAILFINS!! ... click
at ...
visi.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-01-28 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 4:16 [ECOS] Re: Half Duplex RS485 wangcui
2008-01-26 20:41 ` Laurie Gellatly
2008-01-28 10:34 ` wangcui
2008-01-27 4:52 ` [ECOS] Uart missing chars when in Release Laurie Gellatly
2008-01-27 5:14 ` [ECOS] " Grant Edwards
2008-01-27 6:46 ` Laurie Gellatly
2008-01-27 9:54 ` Grant Edwards
2008-01-27 11:20 ` Laurie Gellatly
2008-01-27 15:55 ` Grant Edwards
2008-01-28 0:11 ` Laurie Gellatly
2008-01-28 2:37 ` Grant Edwards
2008-01-28 5:53 ` Laurie Gellatly
2008-01-28 15:58 ` Grant Edwards
2008-01-28 20:40 ` Grant Edwards [this message]
2008-01-29 23:35 ` Byron Jacquot
2008-02-06 9:35 ` Laurie Gellatly
2008-02-06 15:25 ` Grant Edwards
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='fnl79n$16k$1@ger.gmane.org' \
--to=grante@visi.com \
--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).