summaryrefslogtreecommitdiff
path: root/src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp
diff options
context:
space:
mode:
authorBart Oldeman <bart.oldeman@calculquebec.ca>2019-02-03 02:57:10 +0000
committerEric Anholt <eric@anholt.net>2019-02-05 17:53:35 +0000
commita203eaa4f4fb672b95426289b8dad3a8998f92d7 (patch)
treed9f8141ac083bfc79a92b2affc6e39f9ca027c42 /src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp
parent6e5eb4ead62131db3d6570fe8c0d0aa67f0149a9 (diff)
gallium-xlib: query MIT-SHM before using it.
When Mesa is compiled for gallium-xlib using e.g. ./configure --enable-glx=gallium-xlib --disable-dri --disable-gbm -disable-egl and is used by an X server (usually remotely via SSH X11 forwarding) that does not support MIT-SHM such as XMing or MobaXterm, OpenGL clients report error messages such as Xlib: extension "MIT-SHM" missing on display "localhost:11.0". ad infinitum. The reason is that the code in src/gallium/winsys/sw/xlib uses MIT-SHM without checking for its existence, unlike the code in src/glx/drisw_glx.c and src/mesa/drivers/x11/xm_api.c. I copied the same check using XQueryExtension, and tested with glxgears on MobaXterm. This issue was reported before here: https://lists.freedesktop.org/archives/mesa-users/2016-July/001183.html Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Cc: <mesa-stable@lists.freedesktop.org>
Diffstat (limited to 'src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp')
0 files changed, 0 insertions, 0 deletions