Hi Rob, Thanks for this response.
> But my question remains -purely out of interest- why non-rt devices and > rt devices can _fundamentally_ not share an IRQ? > > > > My understanding is adeos-ipipe/xenomai provide an interrupt abstraction > layer underneath Linux. If there is more than one consumer of an > interrupt it has to be copied/forwarded to all those that need it. If > an IRQ is shared with an RT application, and the Linux kernel I would > imagine this would create some level of indeterministic RT software. IRQs are incoming (to the kernel/CPU) signals IIUC. I imagine that at the end of these incoming IRQ's sit ISRs just waiting for IRQ and ready to respond to it in whatever manner they usually do. If this understanding is correct (which it probably is not) then I would not be able to conceive of a reason why the IRQ could not be passed on to the NON RT interrupt service routine after it has been handled by the RT-ISR. But I reiterate that my understanding of these things is as sketchy as my interest to improve the sketchiness is big. :) > This is probably a good question for the xenomai, or adeos-ipipe mailing > list. Have already done so earlier. I was not aware initially that this thread was on the RTnet list. The duplicate and capitalised RTNet in the subject must have been mysteriously obscured by my client for a while. :) Roland > > -Rob _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
