From: Bryan Hilterbrand <bhilterbrand@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Problems with user_irq.c Native example
Date: Wed, 22 Dec 2010 19:11:18 -0700 [thread overview]
Message-ID: <D7352E9EB94BE54D8E052C5D9FE093294798D63DD4@domain.hid> (raw)
In-Reply-To: <1280655383.6700.11.camel@domain.hid>
On Sunday, 2010-08-01, Philippe Gerum wrote:
> Also note that [userland interrupt] support may introduce serious issues
> down the road,
> like not being able to use gdb over your application; using it in new
> apps is a bad idea in the first place, because interrupt handling is
> fundamentally a kernel thing, and should remain so.
>
> Providing this interface was a mistake, it is now deprecated, and
> scheduled for removal in 3.x. The right approach is to process
> (real-time) interrupts in kernel space from a RTDM driver, waking up a
> userland thread as needed. That thread may wait for events via blocking
> ioctl()/read() requests directed at the driver, thus following the
> standard programming model.
I just discovered this thread, and I'm trying to solve a similar problem.
Philippe, can you point me to a RTDM driver example that uses an interrupt
and blocks the reader? Or is this something that I will need to figure out
myself? A good RTDM example would be a start...
I'm on an older version of Xenomai (2.3) if that makes a difference.
Thank you for any help you can give me!
next prev parent reply other threads:[~2010-12-23 2:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 7:03 [Xenomai-help] Problems with user_irq.c Native example Murilo Marinho
2010-08-01 9:36 ` Philippe Gerum
2010-08-01 13:10 ` Henri Roosen
2010-08-02 1:32 ` Flavio de Castro Alves Filho
2010-12-23 2:11 ` Bryan Hilterbrand [this message]
2010-12-23 9:11 ` Philippe Gerum
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=D7352E9EB94BE54D8E052C5D9FE093294798D63DD4@domain.hid \
--to=bhilterbrand@domain.hid \
--cc=rpm@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.