I'm writing a basic device manager that loads a driver for any peripheral that is attached or gets attached to a computer, this part works well, the issue I'm having is that events seem to be dropped during the peripheral call method, specifically I'm using a timer event to mediate my kernel execution and it disappears, I'm curious if this is by design, (like sleep ect) or if I'm being stupid.
0
Peripheral call dropping events
Started by p3p, Apr 13 2015 11:42 PM
4 replies to this topic
#1
Posted 13 April 2015 - 11:42 PM
#3
Posted 13 April 2015 - 11:50 PM
It's by design, but it's by the design of whoever created the peripheral. Not all peripheral calls do it.
#4
Posted 14 April 2015 - 12:33 AM
Ah that's disappointing not sure how to work around events randomly dropping
#5
Posted 14 April 2015 - 01:52 AM
The parallel API is the way to go in this sort of situation. This thread has an example of the sort of code you'd use.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users