Re: [PATCH] Remove XAA

2012-01-19 Thread Dave Airlie
On Wed, Jan 18, 2012 at 8:14 PM, Roman Mamedov r...@romanrm.ru wrote: Hello, I love this. It invalidates some of my outstanding patches in the best possible way. But... could you explain (preferably in the commit message) what evidence you have that it hasn't worked? I thought people were

Re: [PATCH] Remove XAA

2012-01-19 Thread Chris Wilson
On Thu, 19 Jan 2012 09:28:44 +0100, Michel Dänzer mic...@daenzer.net wrote: On Don, 2012-01-19 at 02:14 +0600, Roman Mamedov wrote: I love this. It invalidates some of my outstanding patches in the best possible way. But... could you explain (preferably in the commit message) what

[PATCH SECURITY] XKB: Workaround for CVE-2012-0064: Stop calling UngrabAllDevices().

2012-01-19 Thread Cyril Brulebois
The introduction of XKB debugging functions in the following commit: | commit 7d2543a3cb3089241982ce4f8984fd723d5312a1 | Author: Daniel Stone dan...@fooishbar.org | Date: Wed Dec 29 12:03:01 2010 + | | XKB: Add debug key actions for grabs window tree leads to the ability of bypassing X

Re: [PATCH] Remove XAA

2012-01-19 Thread Daniel Stone
Hi, On 19 January 2012 07:14, Roman Mamedov r...@romanrm.ru wrote: I love this. It invalidates some of my outstanding patches in the best possible way. But... could you explain (preferably in the commit message) what evidence you have that it hasn't worked? I thought people were still using

Re: [PATCH SECURITY] XKB: Workaround for CVE-2012-0064: Stop calling UngrabAllDevices().

2012-01-19 Thread Daniel Stone
Hi, I guess we can decloak this since it's on Phoronix ... On 19 January 2012 21:20, Cyril Brulebois k...@debian.org wrote: The introduction of XKB debugging functions in the following commit: |     XKB: Add debug key actions for grabs window tree leads to the ability of bypassing X screen

[PATCH] UngrabAllDevices: Don't kill clients if not told to

2012-01-19 Thread Daniel Stone
The kill_client argument to UngrabAllClients specifies if we want to kill the client holding the grab or just deactivate the grab. Signed-off-by: Daniel Stone dan...@fooishbar.org Reported-by: Julien Cristau jcris...@debian.org --- dix/grabs.c |3 ++- 1 files changed, 2 insertions(+), 1

Re: [PATCH] UngrabAllDevices: Don't kill clients if not told to

2012-01-19 Thread Cyril Brulebois
Daniel Stone dan...@fooishbar.org (19/01/2012): The kill_client argument to UngrabAllClients specifies if we want to kill the client holding the grab or just deactivate the grab. Signed-off-by: Daniel Stone dan...@fooishbar.org Reported-by: Julien Cristau jcris...@debian.org Reviewed-by:

Re: [PATCH modular] Per-component configure options

2012-01-19 Thread Trevor Woerner
Hi Gaetan, Thanks for reviewing my patch! On Wed, Jan 18, 2012 at 7:49 PM, Gaetan Nadon mems...@videotron.ca wrote: On 12-01-16 06:22 PM, Trevor Woerner wrote: @@ -1009,9 +1017,15 @@ process_module_file() {           continue       fi -     module=`echo $line | cut -d'/' -f1` -    

[PATCH xf86-input-synaptics 0/6] Multitouch support

2012-01-19 Thread Chase Douglas
The following patch series adds multitouch support to synaptics. It starts off by initializing touch support in synaptics.c. Then, we add support to the eventcomm backend. I had hoped to abstract all the touch support between the synaptics.c core and all the backends. This wasn't too hard for

[PATCH xf86-input-synaptics 1/6] Allocate axis labels array dynamically

2012-01-19 Thread Chase Douglas
Signed-off-by: Chase Douglas chase.doug...@canonical.com --- src/synaptics.c | 12 +++- 1 files changed, 11 insertions(+), 1 deletions(-) diff --git a/src/synaptics.c b/src/synaptics.c index b1f2cf2..1c68358 100644 --- a/src/synaptics.c +++ b/src/synaptics.c @@ -993,13 +993,20 @@

[PATCH xf86-input-synaptics 2/6] Add touch device class support

2012-01-19 Thread Chase Douglas
Signed-off-by: Chase Douglas chase.doug...@canonical.com --- configure.ac |5 src/synaptics.c| 65 src/synapticsstr.h | 15 3 files changed, 80 insertions(+), 5 deletions(-) diff --git a/configure.ac

[PATCH xf86-input-synaptics 3/6] eventcomm: Initialize touch device and axes

2012-01-19 Thread Chase Douglas
Use mtdev to ensure touches are tracked and of evdev MT protocol type B. Signed-off-by: Chase Douglas chase.doug...@canonical.com --- configure.ac |8 +++ src/Makefile.am |2 + src/eventcomm.c | 143 +++-- test/Makefile.am |2 +

[PATCH xf86-input-synaptics 4/6] eventcomm: Read evdev events from mtdev where multitouch is available

2012-01-19 Thread Chase Douglas
Signed-off-by: Chase Douglas chase.doug...@canonical.com --- src/eventcomm.c | 23 ++- 1 files changed, 22 insertions(+), 1 deletions(-) diff --git a/src/eventcomm.c b/src/eventcomm.c index 4752568..ada95b2 100644 --- a/src/eventcomm.c +++ b/src/eventcomm.c @@ -66,6 +66,7

[PATCH xf86-input-synaptics 5/6] eventcomm: Add touch event handling

2012-01-19 Thread Chase Douglas
Signed-off-by: Chase Douglas chase.doug...@canonical.com --- src/eventcomm.c | 249 ++- test/fake-symbols.c | 31 +++ 2 files changed, 258 insertions(+), 22 deletions(-) diff --git a/src/eventcomm.c b/src/eventcomm.c index

[PATCH v2 modular] Per-component configure options

2012-01-19 Thread Trevor Woerner
From: Trevor Woerner twoer...@gmail.com Allow a user to specify per-component configure options by providing them in the --modfile file. Any text remaining on a line following a given module/component is assumed to be options which will be passed to the configuration script. Signed-off-by:

[PATCH xf86-input-evdev v4] Copy last valuator values into new touch valuator masks

2012-01-19 Thread Chase Douglas
Evdev is a 100% stateful protocol. The following represents three touches. Two touches begin and end at the same time at (500, 500) and (1000, 1000). The third touch begins after the first two end, and is at (500, 500). ABS_MT_SLOT 0 /* Set touch slot */ ABS_MT_TRACKING_ID

Re: [PATCH v2 modular] Per-component configure options

2012-01-19 Thread Gaetan Nadon
On 12-01-19 04:52 PM, Trevor Woerner wrote: From: Trevor Woerner twoer...@gmail.com Allow a user to specify per-component configure options by providing them in the --modfile file. Any text remaining on a line following a given module/component is assumed to be options which will be passed

Re: [PATCH] Remove XAA

2012-01-19 Thread Aaron Plattner
On 01/18/2012 09:57 PM, Jamey Sharp wrote: On Thu, Jan 19, 2012 at 03:43:39PM +1100, Daniel Stone wrote: On 19 January 2012 04:03, Jamey Sharpja...@minilop.net wrote: I love this. It invalidates some of my outstanding patches in the best possible way. But... could you explain (preferably in

Re: [PATCH] UngrabAllDevices: Don't kill clients if not told to

2012-01-19 Thread Peter Hutterer
On Thu, Jan 19, 2012 at 10:40:32PM +1100, Daniel Stone wrote: The kill_client argument to UngrabAllClients specifies if we want to kill the client holding the grab or just deactivate the grab. Signed-off-by: Daniel Stone dan...@fooishbar.org Reported-by: Julien Cristau jcris...@debian.org

Re: [PATCH 1/2] Only scale direct device touch coordinates

2012-01-19 Thread Peter Hutterer
On Wed, Jan 18, 2012 at 06:04:13PM -0800, Chase Douglas wrote: Indirect touch devices provide valuator values in pure device coordinates. They also don't need to be fixed up for screen crossings. Signed-off-by: Chase Douglas chase.doug...@canonical.com --- dix/getevents.c |7 ++-

Re: [PATCH 1/2] Treat all touch event valuators as absolute

2012-01-19 Thread Peter Hutterer
On Wed, Jan 18, 2012 at 07:09:20PM -0800, Chase Douglas wrote: An indirect touch device, such as a multitouch touchpad, has relative X and Y axes internally. These axes are in screen coordinates. However, the cooresponding axes for touch events are in absolute device coordinates.

Re: [PATCH 1/2] Treat all touch event valuators as absolute

2012-01-19 Thread Chase Douglas
On 01/20/2012 05:28 AM, Peter Hutterer wrote: On Wed, Jan 18, 2012 at 07:09:20PM -0800, Chase Douglas wrote: An indirect touch device, such as a multitouch touchpad, has relative X and Y axes internally. These axes are in screen coordinates. However, the cooresponding axes for touch events are

Re: transset

2012-01-19 Thread Arnaud Fontaine
Hello, Alan Coopersmith alan.coopersm...@oracle.com writes: On 01/18/12 03:43 AM, Arnaud Fontaine wrote: Hello, I merged the code from transset-df, did a lot of cleanup and fixed memory leaks. So I guess that should be fine now, but if anyone is willing to review, that would be great