From: Dan Malek <dan@netx4.com>
To: Claude Robitaille <crobitaille@videotron.ca>
Cc: Graham Stoney <greyham@research.canon.com.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Real Time response/latency question
Date: Tue, 30 Nov 1999 21:18:39 -0500 [thread overview]
Message-ID: <3844857F.82698A18@netx4.com> (raw)
In-Reply-To: Pine.LNX.4.10.9911301917280.1860-100000@localhost.localdomain
Claude Robitaille wrote:
> .... so I have a question: how about interrupt? I guess a very
> simple driver which kicks some userland waiting thread is good enough in
> most cases. Or is there a way to register some userland code?
Interrupts are the reason to write the driver. The open()/close()
can perform some hardware initialization and shutdown to enable
and disable the interrupt source. The interrupt handler may
need to do something to remove the pending interrupt, and then
I usually use select() for the user thread synchronization.
The difficulty registering some user function as the interrupt
handler is it must run with interrupts disabled.....there are
a number of complexities associated with allowing this to
occur. The reason for interrupts disabled is that the handler
must do something to remove the interrupt state before you can
enable interrupts again.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-01 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 3:48 Real Time response/latency question Graham Stoney
1999-11-30 15:28 ` Dan Malek
1999-12-01 0:23 ` Claude Robitaille
1999-12-01 2:18 ` Dan Malek [this message]
1999-12-01 15:34 ` Marcus Sundberg
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=3844857F.82698A18@netx4.com \
--to=dan@netx4.com \
--cc=crobitaille@videotron.ca \
--cc=greyham@research.canon.com.au \
--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).