Peter Hutterer peter.hutte...@who-t.net writes:
A quick git grep shows that timers are used in keybard, mouse, joystick,
synaptics, and wacom, all of those are in the signal path. We could in
theory fix up the lot, but it will take time.
Thanks for checking; it seems like the server really
On Fri, Sep 28, 2012 at 01:25:50AM -0700, Keith Packard wrote:
Peter Hutterer peter.hutte...@who-t.net writes:
Thanks, merged this into my tree. This should fix the remaining issues we're
seeing with synaptics.
Did you see my comments about this patch? I'm really not excited about
On Wed, Oct 3, 2012 at 11:25 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
On Fri, Sep 28, 2012 at 01:25:50AM -0700, Keith Packard wrote:
Peter Hutterer peter.hutte...@who-t.net writes:
Thanks, merged this into my tree. This should fix the remaining issues
we're
seeing with
On Wed, Oct 03, 2012 at 12:26:54PM +0800, Daniel Kurtz wrote:
On Wed, Oct 3, 2012 at 11:25 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
On Fri, Sep 28, 2012 at 01:25:50AM -0700, Keith Packard wrote:
Peter Hutterer peter.hutte...@who-t.net writes:
Thanks, merged this into my
Peter Hutterer peter.hutte...@who-t.net writes:
Thanks, merged this into my tree. This should fix the remaining issues we're
seeing with synaptics.
Did you see my comments about this patch? I'm really not excited about
adding 12 more syscalls per WaitForSomething invocation. Seems like
there
On Sat, Sep 22, 2012 at 09:28:34PM +0800, Daniel Kurtz wrote:
X Input drivers, such as xf86-input-synaptics, tend to do all of their
processing in a SIGIO signal handler. This processing often involves
creating, modifying or canceling a timer. Any of these operations may
modify the global
X Input drivers, such as xf86-input-synaptics, tend to do all of their
processing in a SIGIO signal handler. This processing often involves
creating, modifying or canceling a timer. Any of these operations may
modify the global timers array. Therefore, all accesses of this global
must be done
