SIGIO handling in kdrive
dottedmag at dottedmag.net
Fri Oct 3 22:36:42 PDT 2008
Can anyone remember why does kdrive (hw/kdrive/src/kinput.c) handles
SIGIO on it's own?
I've recently debugged the problem with lost (actually delayed) keypress
which wakes up the device from suspend and also should be processed by X
and found that this keypress is delayed due to SIGIO handler in kdrive.
Under normal circumstances select() in
dix/dispatch.c:Dispatch->WaitForSomething handles new data arriving to
the /dev/misc/input0 properly. SIGIO handler is not called at all.
While resuming from suspend, SIGIO handler on /dev/misc/input0 gets
called and select() does not return, so key processing is delayed until
the timeout of select().
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the xorg