[PATCH] os: Don't listen to 'tcp' by default. Add '-listen' option. [v2]

2014-09-15 Thread Keith Packard
This disables the tcp listen socket by default. Then, it uses a new xtrans interface, TRANS(Listen), to provide a command line option to re-enable those if desired. v2: Leave unix socket enabled by default. Add configure options. Signed-off-by: Keith Packard kei...@keithp.com --- configure.ac

[PATCH] Build required portions of registry.c automatically [v2]

2014-09-15 Thread Keith Packard
Instead of making the inclusion of the registry code a global conditional, split the registry into two pieces; the bits required by the X-Resource extension (the resource names) and the bits required by the XCSECURITY extension (the protocol names). Build each set of code if the related extension

Re: [PATCH] os: Don't listen to 'tcp' by default. Add '-listen' option. [v2]

2014-09-15 Thread Hans de Goede
Hi, On 09/15/2014 05:42 PM, Keith Packard wrote: This disables the tcp listen socket by default. Then, it uses a new xtrans interface, TRANS(Listen), to provide a command line option to re-enable those if desired. v2: Leave unix socket enabled by default. Add configure options.

[PATCH libX11] xcb_io: Fix Xlib 32-bit request number issues

2014-09-15 Thread Jonas Petersen
By design, on 32-bit systems, the Xlib internal 32-bit request sequence numbers may wrap. There is some locations within xcb_io.c that are not wrap-safe though. The value of last_flushed relies on request to be sequential all the time. This is not given in the moment when the sequence has just

Re: [Xcb] [PATCH libX11] xcb_io: Fix Xlib 32-bit request number wrapping bug

2014-09-15 Thread Jonas Petersen
Hi Keith, (2nd try) I went back in time and found your last post regarding this topic. You did make some suggestions that got lost, probably due to my discontinuing. Sorry about that. So let me pick it up again from there, in order to hopefully get the case going. I will post an updated

[PATCH 6/8 v2] modesetting: Connect the driver to the build.

2014-09-15 Thread Eric Anholt
v2: Fix libdrm version check, and use XORG_VERSION_* instead of a static 1.0.0 version for the driver module. Signed-off-by: Eric Anholt e...@anholt.net --- Thanks for the review! I've added my s-o-bs (oops), and added your review to the rest of the patches. modesetting-import branch

Re: [PATCH 6/8 v2] modesetting: Connect the driver to the build.

2014-09-15 Thread Keith Packard
Eric Anholt e...@anholt.net writes: v2: Fix libdrm version check, and use XORG_VERSION_* instead of a static 1.0.0 version for the driver module. Signed-off-by: Eric Anholt e...@anholt.net Reviewed-by: Keith Packard kei...@keithp.com Looks like that was the last of the patches; do you

[PATCH synaptics] Limit the movement to 20 mm per event

2014-09-15 Thread Peter Hutterer
Touchpads are limited by a fixed sampling rate (usually 80Hz). Some finger changes may happen too fast for this sampling rate, resulting in two distinct event sequences: * finger 1 up and finger 2 down in the same EV_SYN frame. Synaptics sees one finger down before and after and the changed

Re: [PATCH synaptics] Limit the movement to 20 mm per event

2014-09-15 Thread Alexander E. Patrakov
16.09.2014 07:08, Peter Hutterer wrote: Touchpads are limited by a fixed sampling rate (usually 80Hz). Some finger changes may happen too fast for this sampling rate, resulting in two distinct event sequences: * finger 1 up and finger 2 down in the same EV_SYN frame. Synaptics sees one finger

Re: [PATCH synaptics] Limit the movement to 20 mm per event

2014-09-15 Thread Alexander E. Patrakov
Oops, sorry. I really must sleep more. I replied with a libinput patch to a synaptics patch. As I no longer use synaptics and don't want to figure out whether the code there allows to say this is a new finger, I just slap an ACK on the original patch. 16.09.2014 08:57, Alexander E. Patrakov

Re: [PATCH synaptics] Limit the movement to 20 mm per event

2014-09-15 Thread Peter Hutterer
On Tue, Sep 16, 2014 at 09:17:12AM +0600, Alexander E. Patrakov wrote: Oops, sorry. I really must sleep more. I replied with a libinput patch to a synaptics patch. As I no longer use synaptics and don't want to figure out whether the code there allows to say this is a new finger, I just slap

Re: [PATCH synaptics] Limit the movement to 20 mm per event

2014-09-15 Thread Peter Hutterer
On Tue, Sep 16, 2014 at 08:57:56AM +0600, Alexander E. Patrakov wrote: 16.09.2014 07:08, Peter Hutterer wrote: Touchpads are limited by a fixed sampling rate (usually 80Hz). Some finger changes may happen too fast for this sampling rate, resulting in two distinct event sequences: * finger 1