Another protocol repository merge attempt

The idea of merging all of our X protocol repositories came up again, and Adam Jackson asked if I wanted to wait for this before merging my randr lease/non-desktop changes. Not really? But, I'm still interested in a merge of the protocol repositories; we've got way too many, and they're mostly

Re: monitor hotplug resolution switch

Johann Obermayr composed on 2017-12-13 15:07 (UTC): > now i have compile 2.99.917 and enable VirtualHeads in the xorg.conf. > xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 > xrandr --addmode VIRTUAL1 "1920x1080" > xrandr --output VIRTUAL1 --mode "1920x1080" > now

AW: monitor hotplug resolution switch

Hello, now i have compile 2.99.917 and enable VirtualHeads in the xorg.conf. xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 xrandr --addmode VIRTUAL1 "1920x1080" xrandr --output VIRTUAL1 --mode "1920x1080" now it looks like it works. The resolution is always

Re: AW: AW: AW: monitor hotplug resolution switch

Le 13/12/2017 à 20:53, Johann Obermayr a écrit : Now I'm search a way to set this 3 line with the xrandr extensions library. did you look here? http://dodin.org/wiki/pmwiki.php?n=Doc.AddXResolution#toc3 it need to be in a script at launch after X starts, for me simply launched by kde

AW: AW: AW: monitor hotplug resolution switch

Hello, > -Ursprüngliche Nachricht- > Von: xorg [mailto:xorg-boun...@lists.x.org] Im Auftrag von j...@dodin.org > Gesendet: Mittwoch, 13. Dezember 2017 20:05 > An: xorg@lists.x.org > Betreff: Re: AW: AW: monitor hotplug resolution switch > > Le 13/12/2017 à 11:14, Johann Obermayr a écrit 

[PATCH xserver 1/2] os: Fix a type error in the IPv6 XDMCP code

Building with strict-aliasing rightly chirps here: ../os/xdmcp.c: In function ‘XdmcpRegisterConnection’: ../os/xdmcp.c:489:31: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] &((struct sockaddr_in6 *) )->sin6_addr.s6_addr[12];

[PATCH xserver 2/2] build: Drop -fno-strict-aliasing

For the autotools build this won't have any effect until a new util-macros package is released. Signed-off-by: Adam Jackson --- configure.ac | 6 -- meson.build | 1 - 2 files changed, 7 deletions(-) diff --git a/configure.ac b/configure.ac index 456a9e0a96..5260f1f082

Re: [PATCH util/macros] Drop -fno-strict-aliasing from XORG_CWARNFLAGS

On Wed, 2017-12-13 at 11:31 -0800, Keith Packard wrote: > Adam Jackson writes: > > > This has been "deprecated" since 2011, but because it is still > > referenced from XORG_DEFAULT_OPTIONS nothing has ever been updated to > > get strict aliasing right. Let's fix that. > > I

Re: Merged repo for protocol headers? Why are they split?

Am 07.12.2017 17:18 schrieb "Emil Velikov" : On 6 December 2017 at 12:37, Daniel Martin wrote: > Hi all, > > if anyone would like to have a look, I've pushed my current work on > the merged proto repo here: >

Re: [PATCH util/macros] Drop -fno-strict-aliasing from XORG_CWARNFLAGS

Adam Jackson writes: > This has been "deprecated" since 2011, but because it is still > referenced from XORG_DEFAULT_OPTIONS nothing has ever been updated to > get strict aliasing right. Let's fix that. I don't understand this -- are you getting rid of this option from our

Re: AW: AW: monitor hotplug resolution switch

Le 13/12/2017 à 11:14, Johann Obermayr a écrit : We are using VNC. so you need a way to set a resolution in VNC, I did that but so long time ago I don't recall how :-( sorry jdd -- http://dodin.org ___ xorg@lists.x.org: X.Org support Archives:

[PATCH util/macros] Drop -fno-strict-aliasing from XORG_CWARNFLAGS

This has been "deprecated" since 2011, but because it is still referenced from XORG_DEFAULT_OPTIONS nothing has ever been updated to get strict aliasing right. Let's fix that. Signed-off-by: Adam Jackson --- xorg-macros.m4.in | 7 +++ 1 file changed, 3 insertions(+), 4

AW: AW: monitor hotplug resolution switch

Hi, Thanks for helping. regards Johann > -Ursprüngliche Nachricht- > Von: xorg [mailto:xorg-boun...@lists.x.org] Im Auftrag von j...@dodin.org > Gesendet: Mittwoch, 13. Dezember 2017 10:22 > An: xorg@lists.x.org > Betreff: Re: AW: monitor hotplug resolution switch > > Le 13/12/2017 à

Re: [PATCH xserver] xfree86: Hold input_lock across SPRITE functions in VGA arbiter

On Wed, 2017-08-02 at 21:34 -0700, Keith Packard wrote: > Avoid scrambling the sprite functions wrapper. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101995 > Signed-off-by: Keith Packard > --- > hw/xfree86/common/xf86VGAarbiterPriv.h | 20 +--- >

[PATCH xserver 2/2] glx: Enable GLX_ARB_create_context_no_error

This is mostly for the client library's convenience, if this extension is listed then it can know the attribute won't be rejected. Note that we don't _do_ anything with this attribute, meaning indirect contexts will not be no-error. That's fine, we don't want to introduce undefined behavior into a

[PATCH xserver 1/2] glx: Stop printing messages about what GLX extensions we enable

glxinfo already exists, use it. Signed-off-by: Adam Jackson --- glx/glxdri2.c | 29 +++-- glx/glxdriswrast.c | 3 --- 2 files changed, 3 insertions(+), 29 deletions(-) diff --git a/glx/glxdri2.c b/glx/glxdri2.c index 2e24b56e6c..28d5a3a9c0 100644

Re: [PATCH xserver] os: Fix strtok/free crash in ComputeLocalClient

On 2017-12-13 04:43 PM, Adam Jackson wrote: > On Tue, 2017-12-12 at 22:18 +0100, Tomasz Śniatowski wrote: >> On 8 December 2017 at 16:46, Michel Dänzer wrote: >>> >>> Hmm. My initial answer was no, since ComputeLocalClient should only be >>> called on the main thread. But if

Re: [PATCH xserver 6/6] os: Remove unused OsRegisterSigWrapper

On Wed, Dec 13, 2017 at 5:15 PM, Adam Jackson wrote: > On Wed, 2017-12-13 at 16:21 +0100, Olivier Fourdan wrote: > > > Note that xf86-video-intel/src/sna/sna_accel.c makes use of > > OsRegisterSigWrapper() and will need updating. > > Ngh. Okay, merged the other five, will defer

Re: [PATCH xserver] meson: Add dependency on generated code fragments in hw/xwin/glx/

On Tue, 2017-10-10 at 13:43 +0100, Jon Turney wrote: > Somehow I'd managed to write this with this dependency missing, so this only > works correctly when the generated files already exist and the correct > automatic dependencies generated, but fails on a clean build. > > Including generated

Re: [PATCH xserver 1/2] os: Add epoll-like pollset implementation for AIX

On Thu, 2017-10-12 at 19:21 -0700, Keith Packard wrote: > Peter Harris writes: > > > AIX's poll only allows FD_SETSIZE entries in the fd list, which is > > insufficient for expanded MaxClients. > > I can't evaluate whether these patches actually do the right thing, but >

Re: [PATCH xserver 6/6] os: Remove unused OsRegisterSigWrapper

On Wed, 2017-12-13 at 16:21 +0100, Olivier Fourdan wrote: > Note that xf86-video-intel/src/sna/sna_accel.c makes use of > OsRegisterSigWrapper() and will need updating. Ngh. Okay, merged the other five, will defer this one until intel is updated. remote: I: patch #189373 updated using rev

AW: monitor hotplug resolution switch

Hello, > -Ursprüngliche Nachricht- > Von: xorg [mailto:xorg-boun...@lists.x.org] Im Auftrag von Felix Miata > Gesendet: Mittwoch, 13. Dezember 2017 11:31 > An: xorg@lists.x.org > Betreff: Re: monitor hotplug resolution switch > > Johann Obermayr composed on 2017-12-13 08:36 (UTC: > > >>

Re: [PATCH xserver] xwayland: Give up “cleanly“ on Wayland socket errors

On Tue, 2017-11-21 at 14:45 +0100, Olivier Fourdan wrote: > Xwayland is a pretty standard Wayland client, we want to be able to > capture core dumps on crashes. > > Yet using "-core" causes any FatalError() to generate a core dump, > meaning that we would get a core file for all Wayland server

Re: [PATCH xserver] os: Fix strtok/free crash in ComputeLocalClient

On Tue, 2017-12-12 at 22:18 +0100, Tomasz Śniatowski wrote: > On 8 December 2017 at 16:46, Michel Dänzer wrote: > > > > Hmm. My initial answer was no, since ComputeLocalClient should only be > > called on the main thread. But if there can be a race with strtok > > getting

Re: [PATCH xserver 6/6] os: Remove unused OsRegisterSigWrapper

On Mon, Nov 20, 2017 at 9:43 PM, Adam Jackson wrote: > Signed-off-by: Adam Jackson > --- > include/os.h | 3 --- > os/osinit.c | 19 --- > 2 files changed, 22 deletions(-) > > diff --git a/include/os.h b/include/os.h > index

Re: [PATCH xserver 5/6] kdrive: remove KdSignalWrapper etc.

On Mon, Nov 20, 2017 at 9:43 PM, Adam Jackson wrote: > This no longer does anything useful. > > Signed-off-by: Adam Jackson > --- > hw/kdrive/src/kdrive.c | 14 -- > 1 file changed, 14 deletions(-) > > diff --git a/hw/kdrive/src/kdrive.c

Re: [PATCH xserver 4/6] xfree86: remove xf86CaughtSignal etc.

On Mon, Nov 20, 2017 at 9:43 PM, Adam Jackson wrote: > This no longer does anything useful. > > Signed-off-by: Adam Jackson > --- > hw/xfree86/common/xf86.h| 2 -- > hw/xfree86/common/xf86Events.c | 11 --- > hw/xfree86/common/xf86Globals.c |

Re: [PATCH xserver 3/6] os: Make OsSignalHandler ask for core dumps for signo != SIGQUIT

On Mon, Nov 20, 2017 at 9:43 PM, Adam Jackson wrote: > SIGQUIT is a normal termination request, but any other signal we handle > here wants a core. This has the effect of making FatalError's call to > AbortServer trigger the > > if (CoreDump) > OsAbort(); > > path.

Re: [PATCH xserver 2/6] xfree86: Remove xf86InterceptSignals

On Mon, Nov 20, 2017 at 9:43 PM, Adam Jackson wrote: > The only consumer of this is the Linux vm86 backend for int10 (which you > should not use), and there all it serves to do is make signals generated > by the vm86 task non-fatal. In practice this error appears never to >

Re: [PATCH xserver 1/6] xfree86: Remove xf86InterceptSigIll

On Mon, Nov 20, 2017 at 9:43 PM, Adam Jackson wrote: > This was added in ~2004 for the sis driver, to detect whether it could > use SSE for memcpy. Charmingly, the code to check whether that feature > exists in the server is: > > #if XORG_VERSION_CURRENT >=

Re: monitor hotplug resolution switch

On Tue, 2017-12-12 at 11:22 +, Johann Obermayr wrote: > Hello, > > i have a x86 machine with i915 graphics. > With connected display (1920x1080) all is ok. > But if I disconnect the monitor, the resolution switch to 320x200. > > How can I disable this ? The X server does not resize

Re: monitor hotplug resolution switch

Johann Obermayr composed on 2017-12-13 08:36 (UTC: >> Johann Obermayr composed: >>> i have a x86 machine with i915 graphics. >>> With connected display (1920x1080) all is ok. >>> But if I disconnect the monitor, the resolution switch to 320x200. >>> How can I disable this ? >>> I will always

Re: [PATCH xserver] os: Fix strtok/free crash in ComputeLocalClient

On 8 December 2017 at 16:46, Michel Dänzer wrote: > On 2017-12-07 11:19 AM, walter harms wrote: >> Am 06.12.2017 12:16, schrieb Tomasz Śniatowski: >>> Don't reuse cmd for strtok output to ensure the proper pointer is >>> freed afterwards. >>> >>> The code incorrectly assumed

Re: AW: monitor hotplug resolution switch

Le 13/12/2017 à 09:36, Johann Obermayr a écrit : root@sigmatek-x86-mp:~# xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected DP1 disconnected HDMI1 disconnected DP2 disconnected HDMI2 disconnected DP3 connected 1920x1080 60.0 + HDMI3

AW: monitor hotplug resolution switch

> -Ursprüngliche Nachricht- > Von: xorg [mailto:xorg-boun...@lists.x.org] Im Auftrag von j...@dodin.org > Gesendet: Dienstag, 12. Dezember 2017 23:30 > An: xorg@lists.x.org > Betreff: Re: monitor hotplug resolution switch > > Le 12/12/2017 à 12:22, Johann Obermayr a écrit : > > Hello, >