Re: [PATCH] Fix format string.

Thomas Klausner w...@netbsd.org writes: It's my first xserver patch, so how do I proceed to get it included? I was told NOT to push there :) You're done; it's on the list and has review, so I'll merge it to the server. Thomas From 8b0bc274d3f77dda32db01274b78fb754a179caf Mon Sep 17

Re: [PATCH] Fix format string.

Am 13.08.2014 09:54, schrieb Keith Packard: Thomas Klausner w...@netbsd.org writes: It's my first xserver patch, so how do I proceed to get it included? I was told NOT to push there :) You're done; it's on the list and has review, so I'll merge it to the server. Thomas From

[PATCH] glamor: Don't call glamor_copy_fbo_cpu() for GLAMOR_DRM_ONLY pixmaps

From: Michel Dänzer michel.daen...@amd.com It results in a crash. Signed-off-by: Michel Dänzer michel.daen...@amd.com --- Looks like I failed to test glamor_copy_fbo_cpu() with piglit before. glamor/glamor_copy.c | 1 + 1 file changed, 1 insertion(+) diff --git a/glamor/glamor_copy.c

[PATCH] linux: Automatically ShareVTs if the VT are already in graphics mode

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 does not install a fbdev for kernel to use for consoles and plymouth

[PATCH] glamor: Free Xv put image data immediately after use

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 visible performance impact. Signed-off-by:

Glamor never frees Xv temporary pixmaps

Keith Packard kei...@keithp.com writes: I don't think the per-port Xv data which glamor allocates is getting freed at server reset time, so I put together a short patch sequence which does it. Seems to work for me at least. I looked into this a bit further yesterday and discovered that glamor

Re: x, y in struct _SynapticsSHM is ABS_X, ABS_Y, why not ABS_MT_POSITION_X, ABS_MT_POSITION_Y?

Hi Peter, Long time no see ;) I recently translated Linux Multi-Touch Protocol to Chinese Simplified https://github.com/openISOFT/Kernel-Document-zh_CN/blob/master/input/multi-touch-protocol.md And hid-egalax, right now it named, hid-multitouch driver`s father ;) Stéphane told about you, I

[PATCH evdev] Make the slot-state per slot

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).

[PATCH evdev 1/2] Fix axis initialization for devices with abs x/y and rel scrollwheels

The Xen Virtual Pointer device has ABS_X, ABS_Y and REL_WHEEL. If smooth scrolling is detected, the current code would first initialize relative axes for scrolling and immediately overwrite those axes when the abs valuators are written out. This patch fixes the default case only, in the case of a

[PATCH evdev 2/2] If only IgnoreRelativeAxes is set, init like a normal relative device

In the current code, if only IgnoreRelativeAxes is set, the code would go on and force absolute axes to initialize even if the relative axes were successfully initialized. Evdev gives precedence to relative axes anyway, initializing absolute axes if the relative axes failed. Thus, if we

Re: [PATCH synaptics] Prevent two-finger taps from being ignored

On Sun, Jul 27, 2014 at 12:58:18PM +0200, Gabriele Mazzotta wrote: When two fingers are used, the coordinates of only one of them is taken into account. This can lead to sudden variations of the absolute coordinates when two-fingers taps are performed if the finger considered changes. Take