Am 14.08.2014 05:43, schrieb Peter Hutterer:
The previous approach only had the slot state for the current slot. If we
changed slots, that means we lost the information if the slot was ever
initialized. If the ABS_MT_TRACKING_ID was never received, the slot would
still update and try to send
On Wed, Aug 13, 2014 at 10:58:54AM +0100, Chris Wilson wrote:
If the VT we are using is already in KD_GRAPHICS mode, calling SETACTIVE
will silently fail. This leads to an indefinite hang as WAITACTIVE never
returns causing lockups on boot. This issue becomes apparent when the
kernel driver
Keith Packard kei...@keithp.com writes:
The Xv StopVideo callback is not invoked on textured video ports, so
the temporary pixmaps allocated for the video planes are never freed.
Freeing the storage immediately after use is a simple solution to this
problem which doesn't appear to have any
Michel Dänzer mic...@daenzer.net writes:
From: Michel Dänzer michel.daen...@amd.com
It results in a crash.
Signed-off-by: Michel Dänzer michel.daen...@amd.com
We really need to figure out how to make GLAMOR_DRM_ONLY go away.
Reviewed-by: Eric Anholt e...@anholt.net
pgp07AyI2W2b9.pgp
The previous approach only had the slot state for the current slot. If we
changed slots, that means we lost the information if the slot was ever
initialized. If the ABS_MT_TRACKING_ID was never received, the slot would
still update and try to send events (which the server refused with a warning).
