On Wed, 2007-06-13 at 10:31 +0200, Peter Feuerer wrote: > > > Great, seems like that's what I'm searching for. I will have a deeper > > > look into this. Because if this is going to be in the mainline kernel, I > > > don't have to touch the kernel at all. > > > > You have to touch it. You still need to write a kernel module which > > handles the interrupt in the first place. > > > > But wouldn't it be a good idea to create a kernel driver which offers an > abstract interface and add it to the mainline kernel or to the preempt > patch? So that handling interrupts can really just happen by coding a > userspace program? > Or is there no way to accomplish that? Sorry if this questions may sound > stupid, I'm not that deep in the code,.. yet. No. This can not work. The kernel side must be able to mask the device interrupt before invoking the user space handler. Otherwise it would not work with shared interrupts. Also the kernel needs control to shut down the device interrupt in case that the user space driver is broken, not running or whatever. Please read the UIO documentation, it explains this in detail. tglx - To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
