Re: multitouch

On Mon, 8 Feb 2010 16:16:35 +1000 Peter Hutterer peter.hutte...@who-t.net said: my apologies for the late answer to this whole thing, but this is sort-of a reply to all three emails by you guys. On Tue, Jan 19, 2010 at 01:00:27PM +0100, Simon Thum wrote: Bradley T. Hughes wrote: On

Re: multitouch

A gesture recogniser instance will be mandatory. However, a client that modifies the list of input devices on demand and quite frequently hopefully won't. Benjamin's approach puts quite a load on the server and on all clients (presence events are sent to every client), IMO unnecessarily.

Re: [PATCH] added labels for multitouch valuators

So here is the new version after corrections of the two patches. ___ xorg-devel mailing list xorg-devel@lists.x.org http://lists.x.org/mailman/listinfo/xorg-devel

[PATCH] added labels for multitouch valuators

Thoses definitions have been included in the kernel but the X server is not updated accordingly. Without these definitions, the multitouch axes are not correctly labelled. Signed-off-by: Benjamin Tissoires tisso...@cena.fr --- Xi/xiproperty.c | 11 +++

[PATCH evdev] Added the names of the valuators for the multitouch properties

Thoses definitions have been included in the kernel but the X server and the evdev driver are not updated accordingly. Without these definitions, the multitouch axes are not correctly labelled. Signed-off-by: Benjamin Tissoires tisso...@cena.fr --- src/evdev.c | 27 +++

Re: [PATCH v2] xrandr: display gamma and brightness

On Feb 06, 10 11:18:21 +0100, Éric Piel wrote: Op 05-02-10 19:30, Matthias Hopf schreef: Any updates on that one? No need to rush, I'd just like to not have this forgotten... Also not from my side :-] Hi, No, no, I haven't forgotten... but I had no time to rework the patch yet.

bitmasks branch

Hi, The bitmasks branch here: http://cgit.freedesktop.org/~sandmann/pixman/log/?h=bitmasks contains the initial reorganization in prepration for the full flags branch. Specifically, it adds the flag fields to the fast path tables, and it changes the fast path checks to be based on

Re: [Mesa3d-dev] [RFC] Event-based buffer validation for DRI2.

Francisco Jerez curroje...@riseup.net writes: Francisco Jerez curroje...@riseup.net writes: The current buffer validation approach (AKA the DRI2 glViewport hack) is both incorrect (because a compliant OpenGL application may opt for the identity as viewport transform and work with window

[dri2proto patch v4] Define an event to notify clients about the validity of their buffers.

Bumps the protocol and package versions. Signed-off-by: Francisco Jerez curroje...@riseup.net --- configure.ac |2 +- dri2proto.h | 19 +-- dri2proto.txt | 31 --- 3 files changed, 42 insertions(+), 10 deletions(-) diff --git a/configure.ac

[xserver patch v4 1/5] Add a PreConfigureWindow hook.

Executed from the ConfigureWindow request, right before sending ConfigureNotify to the clients. This commit breaks the ScreenRec ABI. Signed-off-by: Francisco Jerez curroje...@riseup.net --- dix/window.c |4 hw/xfree86/common/xf86Module.h |6 +++---

[xserver patch v4 2/5] dri2: No need to blit from front on DRI2GetBuffers if they're just being reused.

It can be quite an expensive operation, so we're better off not doing it unless it's totally required. Signed-off-by: Francisco Jerez curroje...@riseup.net --- hw/xfree86/dri2/dri2.c | 42 +++--- 1 files changed, 23 insertions(+), 19 deletions(-) diff --git

[xserver patch v4 3/5] glx: Enforce a 1:1 correspondence between GLX and X11 windows.

The spec says (regarding glXCreateWindow): If there is already a GLXFBConfig associated with win (as a result of a previous glXCreateWindow call), then a BadAlloc error is generated.. It will also come useful to implement DRI2InvalidateBuffers for the indirect case. Signed-off-by: Francisco Jerez

[xserver patch v4 4/5] glx/dri2: Notify the driver when its buffers become invalid.

Signed-off-by: Francisco Jerez curroje...@riseup.net --- glx/glxdri2.c | 28 +--- 1 files changed, 25 insertions(+), 3 deletions(-) diff --git a/glx/glxdri2.c b/glx/glxdri2.c index 0f998de..dae7b42 100644 --- a/glx/glxdri2.c +++ b/glx/glxdri2.c @@ -67,6 +67,7 @@ struct

[xserver patch v4 5/5] dri2: Support the DRI2InvalidateBuffers event.

Bumps the supported DRI2 protocol version. Signed-off-by: Francisco Jerez curroje...@riseup.net --- configure.ac|2 +- hw/xfree86/dri2/dri2.c | 109 +++ hw/xfree86/dri2/dri2.h |5 ++ hw/xfree86/dri2/dri2ext.c | 35

[mesa patch v4 1/3] dri2: Event driven buffer validation.

When a buffer invalidation event is received from the X server, the invalidate hook of the DRI2 flush extension is executed: A generic implementation (dri2InvalidateDrawable) is provided that just bumps the pStamp sequence number in __DRIdrawableRec. For old servers not supporting buffer

[mesa patch v4 2/3] dri/nouveau: Use event driven buffer validation.

--- src/mesa/drivers/dri/nouveau/nouveau_context.c | 33 +--- src/mesa/drivers/dri/nouveau/nouveau_screen.c | 12 2 files changed, 41 insertions(+), 4 deletions(-) diff --git a/src/mesa/drivers/dri/nouveau/nouveau_context.c

[mesa patch v4 3/3] st/dri2: Use event-driven buffer validation.

--- src/gallium/state_trackers/dri/dri_context.c |6 +-- src/gallium/state_trackers/dri/dri_drawable.c | 13 ++ src/gallium/state_trackers/dri/dri_screen.c | 12 ++ src/mesa/SConscript |1 - src/mesa/sources.mak |1 -

Re: [Mesa3d-dev] [xserver patch v4 4/5] glx/dri2: Notify the driver when its buffers become invalid.

Francisco, Will Mesa continue to build after these changes for people who have not tracked the latest glproto and dri2proto repos? I'd prefer to be able to build Mesa on at least the most recently released major distros, which may require the use of some #ifdefs in the changes. Keith On Mon,

Re: [Mesa3d-dev] [xserver patch v4 4/5] glx/dri2: Notify the driver when its buffers become invalid.

Keith Whitwell kei...@vmware.com writes: Francisco, Will Mesa continue to build after these changes for people who have not tracked the latest glproto and dri2proto repos? I'd prefer to be able to build Mesa on at least the most recently released major distros, which may require the use

[PATCH] kdrive: Remove Xfbdev.

Use Xorg with the fbdev driver. Signed-off-by: Adam Jackson a...@redhat.com --- configure.ac| 14 - hw/kdrive/Makefile.am |7 +- hw/kdrive/fbdev/.gitignore |2 - hw/kdrive/fbdev/Makefile.am | 29 -- hw/kdrive/fbdev/Xfbdev.man | 28 -- hw/kdrive/fbdev/fbdev.c

Re: [PATCH] kdrive: Remove Xfbdev.

Twas brillig at 14:27:40 08.02.2010 UTC-05 when a...@redhat.com did gyre and gimble: AJ Use Xorg with the fbdev driver. Nack. Xfree86 DDX is still too heavy to be used in embedded stuff where Xfbdev is used. Let's chop some unneeded bits from Xfree86 first. --

Re: [PATCH] kdrive: Remove Xfbdev.

Twas brillig at 20:30:05 08.02.2010 UTC+01 when dotted...@dottedmag.net did gyre and gimble: AJ Use Xorg with the fbdev driver. MG Nack. Xfree86 DDX is still too heavy to be used in embedded stuff MG where Xfbdev is used. Let's chop some unneeded bits from Xfree86 MG first. And I am

Re: [xserver patch v4 3/5] glx: Enforce a 1:1 correspondence between GLX and X11 windows.

On Mon, Feb 8, 2010 at 1:25 PM, Francisco Jerez curroje...@riseup.net wrote: The spec says (regarding glXCreateWindow): If there is already a GLXFBConfig associated with win (as a result of a previous glXCreateWindow call), then a BadAlloc error is generated.. It will also come useful to

[PULL] Fedora patch merge

Merges some patches I've had sitting in the Fedora tree for too long. Should be pretty uncontroversial. Thanks to Alan Coopersmith for checking my work on the multilib fix. --- The following changes since commit db687f718f760ba254ab51994769db101dc9ca3a: Peter Hutterer (1): xkb: sed

Re: [xserver patch v4 3/5] glx: Enforce a 1:1 correspondence between GLX and X11 windows.

Kristian Høgsberg k...@bitplanet.net writes: On Mon, Feb 8, 2010 at 1:25 PM, Francisco Jerez curroje...@riseup.net wrote: The spec says (regarding glXCreateWindow): If there is already a GLXFBConfig associated with win (as a result of a previous glXCreateWindow call), then a BadAlloc error is

Re: [Mesa3d-dev] [xserver patch v4 4/5] glx/dri2: Notify the driver when its buffers become invalid.

On Mon, 2010-02-08 at 10:41 -0800, Francisco Jerez wrote: Keith Whitwell kei...@vmware.com writes: Francisco, Will Mesa continue to build after these changes for people who have not tracked the latest glproto and dri2proto repos? I'd prefer to be able to build Mesa on at least the

Re: [PATCH] kdrive: Remove Xfbdev.

On Mon, 2010-02-08 at 20:30 +0100, Mikhail Gusarov wrote: Twas brillig at 14:27:40 08.02.2010 UTC-05 when a...@redhat.com did gyre and gimble: AJ Use Xorg with the fbdev driver. Nack. Xfree86 DDX is still too heavy to be used in embedded stuff where Xfbdev is used. Let's chop some

Re: [PATCH] kdrive: Remove Xfbdev.

Twas brillig at 16:07:17 08.02.2010 UTC-05 when a...@nwnk.net did gyre and gimble: AJ Use Xorg with the fbdev driver. Nack. Xfree86 DDX is still too heavy to be used in embedded stuff where Xfbdev is used. Let's chop some unneeded bits from Xfree86 first. AJ [citation needed] 787

Re: [xserver patch v4 3/5] glx: Enforce a 1:1 correspondence between GLX and X11 windows.

On Mon, Feb 8, 2010 at 1:25 PM, Francisco Jerez curroje...@riseup.net wrote: The spec says (regarding glXCreateWindow): If there is already a GLXFBConfig associated with win (as a result of a previous glXCreateWindow call), then a BadAlloc error is generated.. It will also come useful to

Re: [PATCH] kdrive: Remove Xfbdev.

On Mon, 2010-02-08 at 22:12 +0100, Mikhail Gusarov wrote: Twas brillig at 16:07:17 08.02.2010 UTC-05 when a...@nwnk.net did gyre and gimble: AJ Use Xorg with the fbdev driver. Nack. Xfree86 DDX is still too heavy to be used in embedded stuff where Xfbdev is used. Let's chop some

[PATCH] xfree86: Add qxl driver to autodetect logic.

Signed-off-by: Adam Jackson a...@redhat.com --- hw/xfree86/common/xf86AutoConfig.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/hw/xfree86/common/xf86AutoConfig.c b/hw/xfree86/common/xf86AutoConfig.c index 1c4595e..384c7e5 100644 ---

Re: [PATCH] kdrive: Remove Xfbdev.

Twas brillig at 17:28:51 08.02.2010 UTC-05 when a...@nwnk.net did gyre and gimble: AJ [citation needed] 787 664 root S 13628 5.5 0.0 /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1 -nolist 13 megs, compared to 1.4 of Xfbdev. AJ How much of that is .text or

[xserver patch v5 3/5] glx: Enforce a 1:1 correspondence between GLX and X11 windows.

The spec says (regarding glXCreateWindow): If there is already a GLXFBConfig associated with win (as a result of a previous glXCreateWindow call), then a BadAlloc error is generated.. It will also come useful to implement DRI2InvalidateBuffers for the indirect case. Signed-off-by: Francisco Jerez

Re: [PATCH] added labels for multitouch valuators

On Mon, Feb 08, 2010 at 01:50:43PM +0100, Benjamin Tissoires wrote: Thoses definitions have been included in the kernel but the X server is not updated accordingly. Without these definitions, the multitouch axes are not correctly labelled. Signed-off-by: Benjamin Tissoires tisso...@cena.fr

[PATCH video-apm 0/4] Move compiler flags from configure.ac to Makefile.am

Some unsed variables are removed and compiler flags are set in Makefile.am rather than in CFLAGS which is reseerved for the user to override. Applies to these modules: ./driver/xf86-video-apm ./driver/xf86-video-ark ./driver/xf86-video-dummy ./driver/xf86-video-qxl ./driver/xf86-video-vesa

[PATCH video-apm 1/4] config: removed unused variables XORG_INCS and XF86RUSH_INCS

Signed-off-by: Gaetan Nadon mems...@videotron.ca --- configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index aded44e..70f0b0a 100644 --- a/configure.ac +++ b/configure.ac @@ -72,7 +72,7 @@ AC_SUBST([XF86RUSH_LIBS])

[PATCH video-apm 2/4] config: remove unused INCLUDES='-I$(top_srcdir)/src'

This statement is redundant and not used in the makefile Signed-off-by: Gaetan Nadon mems...@videotron.ca --- configure.ac |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index 70f0b0a..ab716d0 100644 --- a/configure.ac +++ b/configure.ac @@

[PATCH video-apm 3/4] config: remove unrequired '-I$(top_srcdir)/src'

The current dir is already included by default in the makefile top_builddir = .. DEFAULT_INCLUDES = -I. -I$(top_builddir) Signed-off-by: Gaetan Nadon mems...@videotron.ca --- configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index

[PATCH video-apm 4/4] config: move compiler flags from configure.ac to Makefile.am

CFLAGS is an automake defined variable that should not be set by the module. It should not be AC_SUBST either, it already is. Use AM_CFLAGS in Makefile.am. This will allow the user to override the flags as they will be in the right order. Signed-off-by: Gaetan Nadon mems...@videotron.ca ---

Re: multitouch

On Mon, Feb 08, 2010 at 06:23:53PM +0900, Carsten Haitzler wrote: There's also the fact that the current approach that Benjamin suggested requires an extra client to manage the slave devices. OTOH, if you're getting serious, there needs to be an instance translating events into