From: Thomas Gleixner <tglx@linutronix.de>
To: Clifford Wolf <clifford@clifford.at>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Interrupt-Handling in User Space
Date: Sat, 05 May 2007 21:55:33 +0200 [thread overview]
Message-ID: <1178394933.31213.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20070505191707.GA9300@clifford.at>
On Sat, 2007-05-05 at 21:17 +0200, Clifford Wolf wrote:
> afaics there is no mechanism in the official kernel tree to handle
> interrupts in user space yet. I'd need that for an embedded project I'm
> woking on atm and are so far not sure if I'm going to implement such a
> generic interface or just write a simple driver that does the job for my
> application. So I'd like to find out what the chances are that such a
> feature will get accepted in the official kernel..
Please take a look at drivers/uio, which is currently in -mm and on the
way to mainline.
tglx
next prev parent reply other threads:[~2007-05-05 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 19:17 Interrupt-Handling in User Space Clifford Wolf
2007-05-05 19:55 ` Thomas Gleixner [this message]
2007-05-05 20:20 ` Sam Ravnborg
2007-05-05 22:00 ` Alan Cox
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=1178394933.31213.22.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=clifford@clifford.at \
--cc=linux-kernel@vger.kernel.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