Re: maxHValue/maxVValue replacement?

On Fri, May 18, 2018 at 12:48:57PM -0400, Adam Jackson wrote: > On Fri, 2018-05-18 at 08:34 +0200, Thomas Klausner wrote: > > Some old drivers use maxHValue/maxVValue, which xorg-server-1.20.0 > > does not provide any longer. What is the proper replacement? > > The only two I was able to find

[ANNOUNCE] xf86-video-rendition 4.2.7

A boring release, adding source compatibility with xserver 1.20. Adam Jackson (2): Move [HV]Total checks into renditionValidMode rendition 4.2.7 Alan Coopersmith (2): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Emil Velikov (1): autogen.sh:

[ANNOUNCE] xf86-video-rendition 4.2.7

A boring release, adding source compatibility with xserver 1.20. Adam Jackson (2): Move [HV]Total checks into renditionValidMode rendition 4.2.7 Alan Coopersmith (2): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Emil Velikov (1): autogen.sh:

[ANNOUNCE] xf86-video-mach64 6.9.6

A boring release, fixing source compatibility with xserver 1.20. Adam Jackson (3): Move max mode h/v checks into ATIValidMode mach64 6.9.6 Alan Coopersmith (2): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Emil Velikov (2): autogen.sh: use

[ANNOUNCE] xf86-video-mach64 6.9.6

A boring release, fixing source compatibility with xserver 1.20. Adam Jackson (3): Move max mode h/v checks into ATIValidMode mach64 6.9.6 Alan Coopersmith (2): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Emil Velikov (2): autogen.sh: use

Re: maxHValue/maxVValue replacement?

On Fri, 2018-05-18 at 08:34 +0200, Thomas Klausner wrote: > Some old drivers use maxHValue/maxVValue, which xorg-server-1.20.0 > does not provide any longer. What is the proper replacement? The only two I was able to find were mach64:

Re: [PATCH xserver 1/2] xfree86: Fix O_CLOEXEC usage in lnx_platform

Michel Dänzer writes: > From: Michel Dänzer > > It was passing O_CLOEXEC as permission bits instead of as a flag. Both are Reviewed-by: Keith Packard -- -keith signature.asc Description: PGP signature

[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #10 from Theo --- (In reply to Michel Dänzer from comment #9) > Created attachment 139609 [details] [review] > Bail from dri2_create_buffer2 if we can't get a pixmap > > Please try this patch on top. This

[PATCH xserver 2/2] modesetting: Pass O_CLOEXEC when opening a DRM device

From: Michel Dänzer We don't want DRM file descriptors to leak to child processes. Signed-off-by: Michel Dänzer --- hw/xfree86/drivers/modesetting/driver.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH xserver 1/2] xfree86: Fix O_CLOEXEC usage in lnx_platform

From: Michel Dänzer It was passing O_CLOEXEC as permission bits instead of as a flag. Signed-off-by: Michel Dänzer --- hw/xfree86/os-support/linux/lnx_platform.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[ANNOUNCE] xf86-video-vmware 13.3.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 xf86-video-vmware is an Xorg display driver for VMware's virtual SGA device. This release provides dri3 support for recent mesa (XA version 2.4+), build support for xserver 1.20, a number of compilation warning fixes, removal of old Xwayland and Xmir

maxHValue/maxVValue replacement?

Some old drivers use maxHValue/maxVValue, which xorg-server-1.20.0 does not provide any longer. What is the proper replacement? Thanks, Thomas ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: