fix gpu hotplugging while VT switched

Maarten mentioned that they were seeing problems with two X servers running and hotplugging the USB output devices. This set adds a cleaner interface for vt owner, it also uses it to queue output devices. Dave. ___ xorg-devel@lists.x.org: X.Org

[PATCH 1/3] xfree86: add VT owner interface

This is just a simple interface to avoid accessing x86Screens[0] directly. Signed-off-by: Dave Airlie airl...@gmail.com --- hw/xfree86/common/xf86.h | 1 + hw/xfree86/common/xf86Events.c | 9 + 2 files changed, 10 insertions(+) diff --git a/hw/xfree86/common/xf86.h

[PATCH 2/3] xf86: use new xf86VTOwnwer interface in a few places

This replaces some previous uses of direct xf86Screens[0] accesses. Signed-off-by: Dave Airlie airl...@gmail.com --- hw/xfree86/common/xf86Events.c | 2 +- hw/xfree86/common/xf86Init.c | 2 +- hw/xfree86/common/xf86Xinput.c | 2 +-

[PATCH 3/3] xf86: don't hotplug output devices while VT switched.

We don't want to hotplug output devices while we are VT switched, as we get races between multiple X servers on the device open, and drm device master status. This just queues device opens until we return from VT switch. Signed-off-by: Dave Airlie airl...@redhat.com ---

Re: fix gpu hotplugging while VT switched

On Wed, Apr 10, 2013 at 04:38:48PM +1000, Dave Airlie wrote: Maarten mentioned that they were seeing problems with two X servers running and hotplugging the USB output devices. This set adds a cleaner interface for vt owner, it also uses it to queue output devices. Series does what it says

Regarding Google Summer Of Code Project for XInput

Hello Sir, I am a programmer studying BTech at IIT. I have a sound background in C, Linux and Java and I am interested in working for X.org as my GSOC project. I have been through the project ideas posted on the URL - http://www.x.org/wiki/SummerOfCodeIdeas. The project in XInput - adding a

[PATCH 1/4] xkb: Add struct XkbCompContext

This commit adds a struct that contains most of the context for starting, running and cleaning up after xkbcomp. Reviewed-by: Daniel Stone dan...@fooishbar.org --- xkb/ddxLoad.c | 76 +-- 1 file changed, 38 insertions(+), 38 deletions(-)

[PATCH 2/4] xkb: Split out code to start and finish xkbcomp

Using the context struct from previous commit, we can now split out code to start xkbcomp and to finish and clean up after it. Reviewed-by: Daniel Stone dan...@fooishbar.org --- xkb/ddxLoad.c | 39 --- 1 file changed, 28 insertions(+), 11 deletions(-) diff

[PATCH 3/4] xkb: Add XkbCompileKeymapFromString()

This new function compiles a keymap from an in-memory string. We use it to add a new keyooard device init function, InitKeyboardDeviceStructFromString(), which inits a keyboard device with a keymap specified as a string instead of a rmlvo set. Reviewed-by: Daniel Stone dan...@fooishbar.org ---

[FYI PATCH 4/4] xwayland: Use InitKeyboardDeviceStructFromString

We can now use this new entry point from xwayland to initialize the keyboard map to what the wayland server sends. Reviewed-by: Daniel Stone dan...@fooishbar.org --- hw/xfree86/xwayland/xwayland-input.c | 55 -- hw/xfree86/xwayland/xwayland-private.h | 5

Re: [PATCH] Xi: Use correct destination when swapping barrier events

On Tue, Apr 09, 2013 at 04:23:19PM -0700, Keith Packard wrote: Write the swapped values to the destination rather than the source. Signed-off-by: Keith Packard kei...@keithp.com merged, will be in the next pull request. thanks. Cheers, Peter --- Xi/extinit.c | 36

Re: [PATCH] Xi: Do not handle ET_TouchOwnership in ProcessTouchEvent

On Tue, Apr 09, 2013 at 11:19:07AM +0200, Maarten Lankhorst wrote: The event struct is different, causing memory corruption on 1.13 and 1.14, as can be witnessed in https://bugs.freedesktop.org/show_bug.cgi?id=56578 Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com thanks,