Hans De Goede 6c984ac9a7 modesetting: Do not use function local static variables ... The modesetting driver may be driving 2 screens (slave and master gpu), which may have different behavior wrt hardware cursor support. So stop using static variables and instead store the hw-cursor support related data in a per screen struct. While at it actually make it per crtc data as in theory different crtc's could have different hw-cursor support. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Keith Packard <keithp@keithp.com>		2016-09-02 13:04:00 -04:00
..
dmx	Switch poll() users to xserver_poll()	2016-07-21 15:04:36 -04:00
kdrive	Switch poll() users to xserver_poll()	2016-07-21 15:04:36 -04:00
vfb	Remove fd_set from Block/Wakeup handler API	2016-07-18 15:27:51 -04:00
xfree86	modesetting: Do not use function local static variables	2016-09-02 13:04:00 -04:00
xnest	Remove fd_set from Block/Wakeup handler API	2016-07-18 15:27:51 -04:00
xquartz	Remove readmask from screen block/wakeup handler	2016-07-18 15:27:51 -04:00
xwayland	wayland: Emulate crossing for native window	2016-08-19 11:04:25 +10:00
xwin	hw/xwin: Update BlockHandler function signature	2016-07-19 08:10:11 -07:00
Makefile.am	Xwayland DDX	2014-04-03 15:19:22 -07:00