Re: [PATCH xserver] dix: Bump MAXHASHSIZE for the resource db

Adam Jackson writes: > #define INITBUCKETS 64 > #define INITHASHSIZE 6 > -#define MAXHASHSIZE 11 > +#define MAXHASHSIZE 16 > > typedef struct _Resource { > struct _Resource *next; > @@ -683,6 +683,16 @@ HashResourceID(XID id, int numBits) > return

Re: xrandr: cannot find output 0x95

When I run xrandr --output 0x95 --off DVI-0 turns off. john@thunderguard:~/.screenlayout$ xrandr --output 0x95 --off john@thunderguard:~/.screenlayout$ xrandr --current Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DisplayPort-3 disconnected HDMI-3 connected

Re: xrandr: cannot find output 0x95

On Tue, Sep 27, 2016 at 11:00:13PM -0400, John Lewis wrote: xrandr --output DisplayPort-3 --off ... DisplayPort-3 disconnected No idea why arandr wants to configure a disconnected output, but this is most likely the cause. Seems an arandr bug. Cheers, Thomas

[ANNOUNCE] xkeyboard-config 2.19

Another regular release: -- Baurzhan Muftakhidinov (1): Add extended Kazakh layout type Benno Schulenberg (4): symbols/rs: Do not specify the key.type where it isn't needed. symbols/rs: Remove pointless trailing "any" and "NoSymbol".

[PATCH xf86-video-omap] Use NotifyFd for drm fd

NotifyFd is available after API 22, and must be used after API 23. Signed-off-by: Hans de Goede --- src/compat-api.h | 4 src/drmmode_display.c | 25 + 2 files changed, 29 insertions(+) diff --git a/src/compat-api.h b/src/compat-api.h

Re: XLookupString return inconsistent

also sprach wetts...@gmail.com [2016-09-29 21:00 +0200]: > I do not know, but I do not see the benefit of doing that. It > certainly would not fix your problem, which I still think is > hardware. I think you are right. I just noticed that this only happens with my USB

Re: XLookupString return inconsistent

> Long story short: do you see any chance in making this bit of > legacy (nostalgia?) code configurable, or remove it altogether? I do not know, but I do not see the benefit of doing that. It certainly would not fix your problem, which I still think is hardware. Andreas

Re: [PATCH 1/4] configure.ac: default to DRI=yes on solaris platforms

Solaris itself only includes DRI & libdrm in Solaris 11 and later - but since that came out in 2011, I'm okay with making it the default case now and requiring anyone wanting to backport a 2016 X server to a release from 2005 (Solaris 10) to have to build libdrm themselves first - I doubt it will

[PATCH xf86-video-voodoo] Remove obsolete miInitializeBackingStore() call

Recent servers do not need this, and the latest servers do not even provide it. Signed-off-by: Hans de Goede --- src/voodoo_driver.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/voodoo_driver.c b/src/voodoo_driver.c index 6ef12ae..04b6d9c 100644 ---

[PATCH 2/3] xfree86: remove aiglx cmd/xorg.conf option

The option is misleading and using it leads to disabling both direct and accelerated indirect GLX. In such cases the xserver GLX attempts to match DRISW (IGLX) configs with the DRI2/3 ones (direct GLX) leading to all sorts of fun experience. Remove the option until we get a clear split and

[PATCH 1/3] glx: drisw is not accelerated IGLX, reflect that in log messages

The messages from glxdricommon.c (used by drisw) still have the A, but at least we're don't have it locally. Cc: Adam Jackson Signed-off-by: Emil Velikov --- glx/glxdriswrast.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 3/3] configure.ac: remove --enable-aiglx option

Presently the option guards both direct and accelerated indirect GLX. As such when one toggles it off they end up without any acceleration. Remove the option all together until we have the time to split/rework things. Cc: Jon Turney Cc: Adam Jackson

[PATCH] glx: remove unused systemTimeExtension

Not even a single DRI2/DRISW driver in mesa ever used this. Appears to be a dri1 artefact copy/pasted in the dri2/drisw codebase. Signed-off-by: Emil Velikov --- glx/glxdri2.c | 1 - glx/glxdricommon.c | 23 --- glx/glxdricommon.h | 2 --

[PATCH 2/4] configure.ac: use $LIBDRM over libdrm when using pkg-config

The former contains the minimum required version which is required. Strictly speaking Xephyr/Xwayland may require version greater than the current 2.3.0, although I've personally haven't checked the specifics. Signed-off-by: Emil Velikov --- configure.ac | 4 ++-- 1

[PATCH 3/4] configure.ac: bump the required libdrm version to 2.3.1

It fixes a bug where the version reported by drmGetLibVersion() was 'wrong'. See libdrm commit 79038751ffe("libdrm: add support for server side functionality in libdrm") for details. Signed-off-by: Emil Velikov --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 4/4] xfree86/dri: remove libdrm runtime checks

As of last commit all the places in our configure.ac require version 2.3.1 (released back in 2007) or later. With the latter introducing the 1.3.0 version, as returned by drmGetLibVersion. Signed-off-by: Emil Velikov --- hw/xfree86/dri/dri.c | 22 +-

[PATCH 1/4] configure.ac: default to DRI=yes on solaris platforms

Afaict there's little-to-no reason/way one would want xserver without DRI support on Solaris platforms. This will allow us to simplify/fix all the libdrm detection in the next commit. Cc: Alan Coopersmith Signed-off-by: Emil Velikov ---

[PATCH xf86-video-vmware] Adapt Block/WakeupHandler signature for ABI 23

Signed-off-by: Hans de Goede --- src/compat-api.h | 5 + 1 file changed, 5 insertions(+) diff --git a/src/compat-api.h b/src/compat-api.h index 205ac59..02876c5 100644 --- a/src/compat-api.h +++ b/src/compat-api.h @@ -75,8 +75,13 @@ #define SCREEN_INIT_ARGS_DECL

[PATCH xf86-video-sisusb] Adapt Block/WakeupHandler signature for ABI 23

Signed-off-by: Hans de Goede --- src/compat-api.h | 5 + 1 file changed, 5 insertions(+) diff --git a/src/compat-api.h b/src/compat-api.h index 6bc946f..89976e4 100644 --- a/src/compat-api.h +++ b/src/compat-api.h @@ -75,8 +75,13 @@ #define SCREEN_INIT_ARGS_DECL

[PATCH xf86-video-opentegra] Adapt Block/WakeupHandler signature for ABI 23

Signed-off-by: Hans de Goede --- src/compat-api.h | 5 + 1 file changed, 5 insertions(+) diff --git a/src/compat-api.h b/src/compat-api.h index bef28ed..294876a 100644 --- a/src/compat-api.h +++ b/src/compat-api.h @@ -76,8 +76,13 @@ #define SCREEN_INIT_ARGS_DECL

Re: some potential security issue for edid-decode

In general, we'd prefer reports of security issues go to our security list (which I've cc'ed) instead of our general discussion list, but in this case, unless I'm missing something, in our code, these are just plain bugs, as there's no trust or privilege boundary someone can exploit here. If

[PATCH xserver v2] Fix id in error when resource does not exist

Always set client->errorValue before returning an error. Test program: #include #include #include #define BAD_VALUE 0xFACE0FF int main(int argc, char *argv[]) { int screen = 0; xcb_connection_t *c = xcb_connect(NULL, ); if (!c) { printf("Cannot connect\n");

[PATCH xserver] dix: Bump MAXHASHSIZE for the resource db

From: Roberto Ragusa [This was originally a workaround for a client-side resource leak: http://lists.freedesktop.org/archives/xorg-devel/2012-November/034555.html Obviously that's a broken app, but the performance problem it illustrates - that walking the linked list

some potential security issue for edid-decode

Hi all, First of all thank you all for the wonderful work you are during in X.org and its components. I have been using x.org and it components forever. Please make sure to CC me in case anybody replies as I have turned off general replies from the list as I'm already info. overloaded. I have

Re: XLookupString return inconsistent

also sprach wetts...@gmail.com [2016-09-12 18:01 +0200]: > > And moments after clicking send, I realized this is really just hardcoding > > US keyboard layout & ASCII encoding - Shift-2 is '@' and Ctrl-@ is '\0'. > > Oh, yes. And Ctrl+3-7 get mapped to 0x1b-0x1f, the control

Re: [PATCH xserver v2] xwayland: Apply "last pointer window" check only to the pointer device

Hi Carlos, > The checks in xwayland's XYToWindow handler pretty much assumes that the > sprite is managed by the wl_pointer, which is not entirely right, given > 1) The Virtual Core Pointer may be controlled from other interfaces, and > 2) there may be other SpriteRecs than the VCP's. > > This

[PATCH xf86-video-qxl] Adjust xspice_wakeup_handler() prototype for building xspice with server 1.19

Signed-off-by: Hans de Goede --- src/spiceqxl_main_loop.c | 4 1 file changed, 4 insertions(+) diff --git a/src/spiceqxl_main_loop.c b/src/spiceqxl_main_loop.c index db89b6d..0ac1f3e 100644 --- a/src/spiceqxl_main_loop.c +++ b/src/spiceqxl_main_loop.c @@ -330,7 +330,11

Re: [PATCH xserver] modesetting: always set a hardware cursor when requested to load one.

Hi, On 28-09-16 16:54, Michael Thayer wrote: Hello Hans, On 28.09.2016 15:37, Hans de Goede wrote: Hi Michael, On 28-09-16 14:47, Michael Thayer wrote: [...] On 09/16/2016 06:52 PM, Michael Thayer wrote: When the X server asks us to load a hardware cursor, that request is always followed