> My understanding is the kernel uses interrupts to count the time and to > trigger timer routines - but these routine are executed in the context they > were registered. A timer created by a process executes in process > context. A driver registered timer executes in kernel context (not interrupt). > Am I wrong? You need to be clear with yourself on the meaning and the types/differences of different contexts first, because its really confusing when you say "kernel context (not interrupt)". > properly. If there is some data to be read from the device it stores it in a > circular buffer. If you're doing it that way then its fine and would work. I agree with your method, but I don't with your understanding of a context. It would be good to read up a little more on this and then come back and ask more questions. Thanks, -Joel -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
