- 28 Sep, 2018 2 commits
-
-
Mesa started supporting GL_OES_EGL_image on llvmpipe in 17.3, after this commit: commit bbdeddd5fd0b797e1e281f058338b3da4d98029d Author: Gurchetan Singh <gurchetansingh@chromium.org> Date: Tue Aug 1 14:49:33 2017 -0700 st/dri: add drisw image extension That's pretty cool, but it means glamor now thinks it can initialize on llvmpipe. This is almost certainly not what anyone wants, as glamor on llvmpipe is pretty much uniformly slower than fb. This fixes both Xorg and Xwayland to refuse glamor in such a setup. Xephyr is left alone, both because glamor is not the default there and because Xephyr+glamor+llvmpipe is one of the easier ways to get xts to exercise glamor. The (very small) downside of this change is that you lose DRI3 support. This wouldn't have helped you very much (since an lp glamor blit is slower than a pixman blit), but it would eliminate the PutImage overhead for llvmpipe's glXSwapBuffers. A future change should add DRI3 support for the fb-only case. Reviewed-by:Eric Anholt <eric@anholt.net> Signed-off-by:
Adam Jackson <ajax@redhat.com>
-
-
- 27 Sep, 2018 2 commits
-
-
No supported driver supports 1bpp anymore, nor has in a very long time. This option only worked with vgahw anyway. Signed-off-by: -
Fixes: accd32a4 (xorg: Remove the XF86PM define.) Signed-off-by:
-
- 26 Sep, 2018 3 commits
-
-
Emma Anholt authored
Inspired by the previous bug, build something we can use to write damage testcases, including testing for the bug. Signed-off-by: -
The mode (CoordModeOrigin or CoordModePrevious) was not taken into account when computing the box. The result was a bad drawing of points in some situations (on my hardware/software configuration, calling XDrawString followed by XDrawPoints in the mode CoordModePrevious). Signed-off-by:
Cedric Roux <sed@free.fr> Signed-off-by:
-
So we do not lose subpixel precision in Xwayland. Suggested-by:
Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com> Closes: libinput/libinput#138
-
- 25 Sep, 2018 9 commits
-
-
Jon Turney authored
Signed-off-by:
Jon Turney <jon.turney@dronecode.org.uk> Reviewed-by:
Colin Harrison <colin.harrison@virgin.net>
-
Jon Turney authored
Seems like this was omitted in error Signed-off-by:
-
Jon Turney authored
v2: Fix a bogus warning about a missing pixelformat attribute issued for every pixelformat when WGL_ARB_framebuffer_sRGB isn't available Signed-off-by:
-
Jon Turney authored
Future work: To properly support GLX_ARB_create_context in indirect mode, we need to use wglCreateContextAttribsARB() rather than wglCreateContext(), when attribs are provided, rather than just dropping attribs on the floor, as we currently do. That probably entails removing the deferred context creation and instead using a temporary window, as direct WGL does. Signed-off-by:
-
Jon Turney authored
v2: Set renderType more correctly Signed-off-by:
-
Jon Turney authored
Signed-off-by:
-
Jon Turney authored
In glxWinSetPixelFormat() handle the case where wglChoosePixelFormatARB() fails and fallback to ChoosePixelFormat() It seems for some drivers, wglChoosePixelFormatARB() can fail when the provided DC doesn't belong to the driver (e.g. it's a compatible DC for a bitmap, so allow a fallback to ChoosePixelFormat() if it fails. Signed-off-by:
-
Jon Turney authored
Exposing these pixelFormats is problematic: they are provided by the 'GDI Generic' renderer, which doesn't support the same set of extensions as the IGD providing the more capable pixelFormats. Signed-off-by:
-
musl only implements inx/outx on x86, so check for __GLIBC__ instead of __linux__. Signed-off-by:Ross Burton <ross.burton@intel.com>
-
- 20 Sep, 2018 1 commit
-
-
Ross Burton authored
Instead of fetching just the sdkdir variable of xorg-server using pkg-config, simply get all of the CFLAGS. Aside from completeness, this helps builds in sysroots as pkg-config knows what to do with --cflags but doesn't remap arbitrary variables. Signed-off-by:
-
- 19 Sep, 2018 4 commits
-
-
Prodding the builder's filesystem for tmp dirs doesn't necessarily tell you anything about what the actual host's filesystem is going to look like, so we should just try the dirs at runtime. Signed-off-by: -
Signed-off-by: -
Emma Anholt authored
I don't think this is useful information to have in the log, and it's a bunch of autotools and meson logic to produce it. Signed-off-by: -
Emma Anholt authored
Signed-off-by:
-
- 12 Sep, 2018 19 commits
-
-
Adam Jackson authored
60ec8ead broke the autotools build: sdksyms.o:(.data+0x58): undefined reference to `InitConnectionLimits' sdksyms.o:(.data+0x2ec8): undefined reference to `xf86ServerName' collect2: error: ld returned 1 exit status Makefile:811: recipe for target 'Xorg' failed Likewise 3a4d7c79 for InitConnectionLimits. Signed-off-by:
-
Only the mga XAA code ever set this (hence the compat macro), since XAA is long gone this can go too. Signed-off-by: -
This was dangerous on UMS and largely pointless on KMS.
-
If it's really this important we should just do it and not complain. We never do it so it must not matter. Signed-off-by: -
I'm sure printing the address of function pointers in modules you'd loaded might have made sense back when we rolled our own dlopen, but we got better. Signed-off-by: -
xf86AllocateScreen() callocs these for us. Signed-off-by: -
Signed-off-by: -
No idea which cult's cargo I was looking at there. Cuts about a minute off the build time. Signed-off-by: -
This variable was no longer being read anywhere. MAXCLIENTS the macro is the compile-time maximum limit, LIMITCLIENTS the macro is the default limit, LimitClients the variable is the limit for the current server. Signed-off-by: -
The old code would not in fact validate the option value, though it might complain about it in the log. It also didn't let you set some legal values that the -maxclients command line option would. Signed-off-by: -
DGAShutdown() walks every screen and attempts to reset the mode. That's maybe a reasonable thing to do, although the explicit loop is certainly a bad smell. In ddxGiveUp it's called after we've torn down the vga arbiter - and in fact most of the rest of screen state - which is... very very bad. The other place it's called is from the Control-Alt-BackSpace handler, where we don't even attempt to do vga arb setup, and where in any case we're going to escape the main loop eventually anyway. Move all that cleanup work inside DGACloseScreen. This means it happens earlier in server teardown than previously, but not in a way you're ever going to be upset about. Signed-off-by: -
Signed-off-by: -
If we set the handler to the thing it's already set to, that's fine. Signed-off-by: -
Dave Airlie authored
Coverity complains about a use after free in here after the freeing, I can't follow the linked list so well, but whot says the device can only be on one list once, so break should fix it. Signed-off-by:Dave Airlie <airlied@redhat.com>
-
Dave Airlie authored
Pointed out by coverity. Signed-off-by: -
Dave Airlie authored
Pointed out by coverity. Signed-off-by: -
Dave Airlie authored
Pointed out by coverity. Signed-off-by: -
Dave Airlie authored
This saves us having to make sure we clean it up. Pointed out by coverity. Signed-off-by: -
Dave Airlie authored
This is created using XNFstrdup, so it needs to be freed. Pointed out by coverity. Signed-off-by:
-
