From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] RedBoot serial rx interrupts
Date: Sat, 13 Jan 2001 07:17:00 -0000 [thread overview]
Message-ID: <XFMail.20010113081726.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <20010112171320.A28773@visi.com>
On 12-Jan-2001 Grant Edwards wrote:
>
> I've got RedBoot running fine without network support. It's
> using polled serial I/O: the individual serial Rx interrupts
> are unmasked but the global interrupt mask is set.
>
> [Why are interrupts being unmasked when polled I/O is being
> used?]
>
It should not. Where are you seeing this [which file/line]?
> When I add network support, the global interrupt mask is
> cleared; cyg_hal_plf_serial_isr then consumes all of input
> data. RedBoot is still calling cyg_hal_plf_serial_getc() to
> try to read input, but it never sees any because it's all being
> consumed by the interrupt routine.
>
> Can anybody point me to something that explains RedBoot's use
> of interrupts?
>
RedBoot does not use interrupts.
> Is the network stack interrupt driven?
>
RedBoot's stack does not. eCos' does of course.
> Why does including network support clear the global interrupt
> mask bit?
>
It does not - or should not - for RedBoot.
> When is serial I/O interrupt driven?
>
Only when you use the serial I/O functions (serial_write, etc).
Are you sure about all of these questions? RedBoot absolutely _never_
touches interrupts. The only time interrupts are used is by eCos
applications.
next prev parent reply other threads:[~2001-01-13 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 15:09 Grant Edwards
2001-01-13 7:17 ` Gary Thomas [this message]
2001-01-13 12:37 ` Grant Edwards
2001-01-13 12:52 ` Gary Thomas
2001-01-13 12:57 ` Grant Edwards
2001-01-13 13:45 ` Grant Edwards
2001-01-13 14:11 ` Gary Thomas
2001-01-13 14:31 ` Grant Edwards
2001-01-13 15:13 ` Gary Thomas
2001-01-13 15:32 ` Grant Edwards
2001-01-15 4:02 ` Nick Garnett
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=XFMail.20010113081726.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.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).