Re: [PATCH xserver] glx/dri2: Don't include drm headers

On Thursday, 6 October 2016, Adam Jackson wrote: > They're not needed, and they won't be present on win32. > > Signed-off-by: Adam Jackson > Reviewed-by: Emil Velikov Pardon the html formatting. Emil

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

On Thu, 2016-10-06 at 14:06 -0400, Peter Harris wrote: > On 2016-10-06 1:07 PM, Adam Jackson wrote: > > ... imagine ChangeGC specifying more than one of {tile, stipple, font, > > clipmask pixmap}.  Whichever one is looked up last will be the > > errorValue thrown with the eventual BadMatch, which

[PATCH xserver] glx/dri2: Don't include drm headers

They're not needed, and they won't be present on win32. Signed-off-by: Adam Jackson --- glx/glxdri2.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/glx/glxdri2.c b/glx/glxdri2.c index c2dab90..484b4ae 100644 --- a/glx/glxdri2.c +++ b/glx/glxdri2.c @@ -31,7 +31,6 @@

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

On 6 October 2016 at 19:02, Jon Turney wrote: > On 29/09/2016 18:41, Emil Velikov wrote: >> >> 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

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

On 29/09/2016 18:41, Emil Velikov wrote: 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

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

On 2016-10-06 1:07 PM, Adam Jackson wrote: > On Thu, 2016-09-29 at 11:17 -0400, Peter Harris wrote: >> Always set client->errorValue before returning an error. > > As sensible as this seems, I think it's wrong. I ran across something > similar a few years ago: > >

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

On Thu, 2016-09-29 at 11:17 -0400, Peter Harris wrote: > Always set client->errorValue before returning an error. As sensible as this seems, I think it's wrong. I ran across something similar a few years ago: https://lists.freedesktop.org/archives/xorg-devel/2011-June/023462.html BadMatch

[PATCH rendercheck] Report results on a per-test basis

This allows a runner such as EzBench to track each test individually and not limit the resolution to groups. This feature can be triggered by using the -r parameter. Signed-off-by: Martin Peres --- main.c| 12 ++ rendercheck.h | 4 ++-- tests.c

Re: [xserver] input: fix VT switch disabling devices

Hi, On 24-09-16 19:55, Mihail Konev wrote: Make sure device removes are processed before doing a VT switch, so that no removes are "overwritten" with attachments afterwards (before the main thread releases the input lock, letting them be processed), which would leave affected devices disabled.

Re: [PATCH xserver v2 1/2] xf86Cursor: Use PRIME master xf86CursorScreenRec::HotX/Y for slaves

Hi, On 06-10-16 11:45, Michel Dänzer wrote: From: Michel Dänzer xf86CursorScreenRec::HotX/Y contain 0 for PRIME slave screens. Fixes incorrect HW cursor position on PRIME slave screens. Also hoist the hotspot translation out from xf86ScreenSet/MoveCursor to

[PATCH xserver v2 2/2] xf86Cursor: Take the input lock in xf86Set/MoveCursor

From: Michel Dänzer Prevents the HW cursor from intermittently jumping around when the cursor image is changed while the cursor is being moved. This is hardly noticeable in normal operation but can be quite confusing when stepping through these codepaths in a debugger.

[PATCH xserver v2 1/2] xf86Cursor: Use PRIME master xf86CursorScreenRec::HotX/Y for slaves

From: Michel Dänzer xf86CursorScreenRec::HotX/Y contain 0 for PRIME slave screens. Fixes incorrect HW cursor position on PRIME slave screens. Also hoist the hotspot translation out from xf86ScreenSet/MoveCursor to xf86Set/MoveCursor, since the hotspot position is a