by support »
Hello,
I'm not familiar with RTAI, but I suppose that the name of the game is interrupt latency and the scheduling latency of the process that is woken up by the interrupt service routine.
So this boils down to how hard real-time constraints are enforced on these. If you need to make modifications Xillybus' driver for Linux, the sources are available of course.
Other than that, I can't comment much. But frankly, I would expect no software hacking required. I mean, enforcing the latency of an interrupt has nothing to do with the driver registered to it, and neither has enforcing scheduling of a process. But this is up to how RTAI is designed and used.
Hoped this helped a bit.
Eli
Hello,
I'm not familiar with RTAI, but I suppose that the name of the game is interrupt latency and the scheduling latency of the process that is woken up by the interrupt service routine.
So this boils down to how hard real-time constraints are enforced on these. If you need to make modifications Xillybus' driver for Linux, the sources are available of course.
Other than that, I can't comment much. But frankly, I would expect no software hacking required. I mean, enforcing the latency of an interrupt has nothing to do with the driver registered to it, and neither has enforcing scheduling of a process. But this is up to how RTAI is designed and used.
Hoped this helped a bit.
Eli