Hi all, I'm trying to track down a problem with SDL missing events from a gaming wheel. It looks like it's not seeing a 'section' of events and this results in an axis from the wheel/joystick being stuck on. If I simultaneously use evtest to monitor the same /dev/input/eventX I see all the events in evtest, but not in SDL. I suspect that some scheduling (or other business) is causing SDL not to check the file handle, and as a result the input system is dropping/resyncing the interface. Can anyone here confirm the behaviour under the situation that one client is busy? What is the maximum time it can be 'away' or what is the size of the inline buffer? Many thanks, Simon. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
