On Wed, May 11, 2011 at 2:53 AM, Dave Airlie airl...@gmail.com wrote:
Hey,
So we got a bug reported against F15 where we were getting an illegal
input event type 0, after passing it around the RH X team I eventually
came to look at it.
The problem appears to be that we are using llvmpipe as
On Thu, May 12, 2011 at 09:45:14AM -0400, Kristian Høgsberg wrote:
A different solution could be to use the input thread idea and stop
taking SIGIO.
The input thread needs a lot of work though - we don't do any locking at
all. So try doing device creation/destruction in a loop, or changing
the
Hey,
So we got a bug reported against F15 where we were getting an illegal
input event type 0, after passing it around the RH X team I eventually
came to look at it.
The problem appears to be that we are using llvmpipe as our swrast
renderer and on systems that fallback to that we end up with
On 05/10/11 11:53 PM, Dave Airlie wrote:
The problem appears to be that we are using llvmpipe as our swrast
renderer and on systems that fallback to that we end up with threads
inside the X server, that we didn't spawn. It appears SIGIO gets
delivered to one of these threads while the main
