Re: List display device names

On Wed, 11 Nov 2015 22:06:12 + Emil Velikov wrote: > Hi Tom, > > On 11 November 2015 at 13:31, Tom Deseyn wrote: > > Hi all, > > > > To configure X I need to know the display device names (e.g. DFP-0). I get > > these by looking at the Xorg.log. Is there a way to list these display > > devi

[PATCH xserver 15/20] render: Use OsTimer for animated cursor timing

This replaces the block/wakeup handlers with an OsTimer. This also avoids problems with performing rendering during the wakeup handler. Signed-off-by: Keith Packard --- render/animcur.c | 57 +--- 1 file changed, 30 insertions(+), 27 deletions(

[PATCH xserver 14/20] os/xdmcp: Replace xdmcp block/wakeup handlers with timer and NotifyFd

This removes the block and wakeup handlers and replaces them with a combination of a NotifyFd callback and timers. Signed-off-by: Keith Packard --- os/xdmcp.c | 114 +++-- 1 file changed, 36 insertions(+), 78 deletions(-) diff --git a/os/x

[PATCH xserver 06/20] config: Use NotifyFd for dbus interface

This uses the NotifyFd interface to monitor the dbus socket rather than a block/wakeup handler. Signed-off-by: Keith Packard --- config/dbus-core.c | 16 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/config/dbus-core.c b/config/dbus-core.c index 8351ea4..3c85ad7

[PATCH xserver 16/20] hw/xfree86: Use NotifyFd for device and other input fd wakeups

Remove code in xf86Wakeup for dealing with device and other input and switch to using the new NotifyFd interface. Signed-off-by: Keith Packard --- hw/xfree86/common/xf86Events.c | 67 -- 1 file changed, 26 insertions(+), 41 deletions(-) diff --git a/hw/xf

[PATCH xserver 19/20] Remove fd_set from Block/Wakeup handler API

This removes the last uses of fd_set from the server interfaces outside of the OS layer itself. Signed-off-by: Keith Packard --- Xext/sleepuntil.c | 17 +++-- Xext/sync.c | 12 ++-- dix/dixfonts.c | 7 +++ dix/dixutils.c

[PATCH xserver 17/20] os: Use NotifyFd interface for listen descriptors

Replace the custom path for dealing with new incoming connections with the general-purpose NotifyFd API. Signed-off-by: Keith Packard --- include/os.h| 3 -- os/WaitFor.c| 4 --- os/connection.c | 104 +++- 3 files changed, 42 inser

[PATCH xserver 20/20] mi: Remove miPointerRec from API

This moves the definition of miPionterRec from mipointrst.h to mipointer.c so that it is no longer visible in the API, allowing it to be changed while the API/ABI is frozen. Signed-off-by: Keith Packard --- mi/mipointer.c | 12 mi/mipointrst.h | 12 2 files changed, 12

[PATCH xserver 12/20] hw/xwayland: Use NotifyFd handler to monitor wayland socket

Replace the block/wakeup handler with a NotifyFd callback instead. Signed-off-by: Keith Packard --- hw/xwayland/xwayland.c | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/hw/xwayland/xwayland.c b/hw/xwayland/xwayland.c index e31becf..bea2164 100644 --- a/

[PATCH xserver 01/20] Remove non-smart scheduler. Don't require setitimer.

This allows the server to call GetTimeInMillis() after each request is processed to avoid needing setitimer. -dumbSched now turns off the setitimer. Signed-off-by: Keith Packard --- configure.ac| 2 +- dix/dispatch.c | 17 ++--- include/dix-config.h.in | 3 +++

[PATCH xserver 18/20] Remove readmask from screen block/wakeup handler

With no users of the interface needing the readmask anymore, we can remove it from the argument passed to these functions. Signed-off-by: Keith Packard --- composite/compalloc.c | 4 ++-- dix/dixutils.c | 14 ++ exa/exa.c

[PATCH xserver 05/20] dix: Switch to the libXfont2 API (v2)

This new libXfont API eliminates exposing internal X server symbols to the font library, replacing those with a struct full of the entire API needed to use that library. v2: Use libXfont2 instead of libXfont_2 Signed-off-by: Keith Packard --- Xext/xf86bigfont.c | 4 +- configure.ac

[PATCH xserver 13/20] Xext/xselinux: Use NotifyFd interface

Replace block/wakeup handlers with SetNotifyFd. Much nicer now. Signed-off-by: Keith Packard --- Xext/xselinux_hooks.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/Xext/xselinux_hooks.c b/Xext/xselinux_hooks.c index d9f2f68..2d85928 100644 --- a/Xext/xs

[PATCH xserver 04/20] dix: Move InitFonts up above screen initialization

Font initialization was split into two stages, the first was to set up font privates with a call to ResetFontPrivateIndex, then much later the call to InitFonts to set up all of the FPEs. Doing the full font initialization before initializing the video drivers means that we can move the call to Res

[PATCH xserver 11/20] modesetting: Use NotifyFd for drm event monitoring

Replace the block/wakeup handlers with a NotifyFd callback. Signed-off-by: Keith Packard --- hw/xfree86/drivers/modesetting/vblank.c | 16 +--- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/hw/xfree86/drivers/modesetting/vblank.c b/hw/xfree86/drivers/modesetting/vbl

[PATCH xserver 03/20] os: Implement support for NotifyFd X_NOTIFY_WRITE

This adds the ability to be notified when a file descriptor is available for writing. Signed-off-by: Keith Packard --- os/WaitFor.c| 30 -- os/connection.c | 40 +++- os/io.c | 8 os/osdep.h | 5 - 4

[PATCH xserver 10/20] kdrive/ephyr: Use NotifyFd for XCB connection input [v2]

Eliminates polling every 20ms for device input. v2: rename ephyrPoll to ephyrXcbNotify and fix the API so it can be used directly for SetNotifyFd. Thanks to Daniel Martin Signed-off-by: Keith Packard Cc: Daniel Martin --- hw/kdrive/ephyr/ephyr.c | 6 -- hw/kdrive/ephyr/ephyr.h | 3

[PATCH xserver 07/20] config: Use NotifyFd interface for udev

This uses the NotifyFd interface to monitor the udev file descriptor rather than adding another block/wakeup handler Signed-off-by: Keith Packard --- config/udev.c | 45 - 1 file changed, 16 insertions(+), 29 deletions(-) diff --git a/config/udev.c b/

[PATCH xserver 02/20] os: Add NotifyFd interfaces

This provides a callback-based interface to monitor file descriptors beyond the usual client and device interfaces. Modules within the server using file descriptors for reading and/or writing can call Bool SetNotifyFd(int fd, NotifyFdProcPtr notify_fd, int mask, void *data); mask can be any

[PATCH xserver 09/20] hw/kdrive: Use NotifyFd for kdrive input devices

This switches the kdrive code to use FD notification for input devices, rather than the block and wakeup handlers. Signed-off-by: Keith Packard --- hw/kdrive/src/kinput.c | 28 ++-- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/hw/kdrive/src/kinput.c b/h

[PATCH xserver 08/20] hw/kdrive: Use NotifyFd interface for kdrive/linux APM monitoring

Replace the block/wakeup handlers with a NotifyFd callback Signed-off-by: Keith Packard --- hw/kdrive/linux/linux.c | 17 - 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/hw/kdrive/linux/linux.c b/hw/kdrive/linux/linux.c index 73a8169..a52bdef 100644 --- a/hw/kdri

Re: [PATCH xf86-input-libinput 3/3] Split mixed pointer/keyboard devices into two separate X devices

On Thu, Nov 12, 2015 at 10:27:05AM +1000, Peter Hutterer wrote: > The server struggles with devices that are both, the protocol (especially XI2) > requires a fairly strict separation of pointer vs keyboard devices. Though the > server has a couple of hacks to route events correctly, mixed > devices

Re: [PATCH xf86-input-libinput 3/3] Split mixed pointer/keyboard devices into two separate X devices

Peter Hutterer writes: > + while (o) { > + iopts = input_option_new(iopts, > + xf86OptionName(o), > + xf86OptionValue(o)); > + o = xf86NextOption(o); > + } Everything else was quite clear u

Re: [PATCH evdev] Only map x and y to axes 0 and 1

Peter Hutterer writes: > The Logitech G600 has one device with all axes north of ABS_MISC. The current > code assigns ABS_MISC as first axis to map to axis 0, i.e. x. On button press, > one node sends the BTN_LEFT but the other node sends an ABS_MISC with a 1 0 > value. ABS_MISC is mapped to axis

Re: [PATCH xserver 1/5] glamor: Handle GL_OUT_OF_MEMORY when allocating texture images.

Eric Anholt writes: > I think it's a safe enough assumption that we're not generating non-OOM > errors. And, now that we're logging errors, we should get reports of > them sooner than we used to. Would it be sensible to wrap the glGetError call like this? GLenum glamor_check_gl_oom() {

[PATCH xf86-input-libinput 2/3] Copy the device capabilities to the X driver struct

And use those copied caps instead of the direct device capability calls. No functional changes at this point, this is preparation work for selectively disabling capabilities on a device. Signed-off-by: Peter Hutterer --- src/xf86libinput.c | 34 ++ 1 file changed

[PATCH xf86-input-libinput 1/3] Split type_name detection out into a helper function

No functional changes Signed-off-by: Peter Hutterer --- src/xf86libinput.c | 32 +--- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/src/xf86libinput.c b/src/xf86libinput.c index 95e2d20..be0ec5d 100644 --- a/src/xf86libinput.c +++ b/src/xf86libinput.

[PATCH xf86-input-libinput 3/3] Split mixed pointer/keyboard devices into two separate X devices

The server struggles with devices that are both, the protocol (especially XI2) requires a fairly strict separation of pointer vs keyboard devices. Though the server has a couple of hacks to route events correctly, mixed devices still experience bugs like [1]. Instead of advertising the device as a

Re: [PATCH xserver 10/11 v2] glamor: Delay making pixmaps shareable until we need to.

Michel Dänzer writes: > On 11.11.2015 06:41, Eric Anholt wrote: >> If a pixmap isn't getting exported as a dmabuf, then we don't need to >> make an EGLImage/GBM bo for it. This should reduce normal pixmap >> allocation overhead, and also lets the driver choose non-scanout >> formats which may be

Re: [PATCH xserver 1/5] glamor: Handle GL_OUT_OF_MEMORY when allocating texture images.

Keith Packard writes: > Eric Anholt writes: > >> +if (glGetError() == GL_OUT_OF_MEMORY) { > > It seems like you'll need to call this in a loop in case multiple error > bits are set? > > And, don't you need to call this (repeatedly) before the function which > might generate an error in case

Re: List display device names

Hi Tom, On 11 November 2015 at 13:31, Tom Deseyn wrote: > Hi all, > > To configure X I need to know the display device names (e.g. DFP-0). I get > these by looking at the Xorg.log. Is there a way to list these display > device names which is more suitable for automation? I looked at xrandr, but >

please do not use &fullrelvers; in xdmcp.xml

Hello Xorg developers, While furthering Debian's multiarch capabilities I ran into the issue that an xdmcp.txt generated from xdmcp.xml (in libxdmcp) would be dependent on the version of xorg-sgml-doctools. Due to the implementation of multiarch, the difference in file content breaks the installat

List display device names

Hi all, To configure X I need to know the display device names (e.g. DFP-0). I get these by looking at the Xorg.log. Is there a way to list these display device names which is more suitable for automation? I looked at xrandr, but I haven't found an option which outputs these names. Thanks, Tom _

[PATCH evdev] Only map x and y to axes 0 and 1

The Logitech G600 has one device with all axes north of ABS_MISC. The current code assigns ABS_MISC as first axis to map to axis 0, i.e. x. On button press, one node sends the BTN_LEFT but the other node sends an ABS_MISC with a 1 0 value. ABS_MISC is mapped to axis 0, this moves the pointer to (0,

Re: [PATCH:xf86-video-modesetting] Fix build when XSERVER_PLATFORM_BUS is not defined.

On Mon, Nov 09, 2015 at 03:43:44PM -0500, Adam Jackson wrote: > On Fri, 2015-11-06 at 10:30 +0100, Thomas Klausner wrote: > > From: Jared McNeill > > It's not wrong, but this driver lives in-server now. Thanks for the information. I have attached anew patch against the xserver. Thomas >From 12