x11perf putimagexy10 extremly slow for glamor on i965

Hi, I have observed extremly low x11perf-putimagexy10 results when using glamor on top of the i965 driver - while shmput10 results are quite ok. First I thought this was limited to intel haswell, but my old arrandale system is affected as well: x11perf -putimagexy10: 1200 reps @ 6.1682 msec (

Re: x11perf putimagexy10 extremly slow for glamor on i965

Clemens Eisserer writes: > Hi, > > I have observed extremly low x11perf-putimagexy10 results when using > glamor on top of the i965 driver - while shmput10 results are quite > ok. Why do you care? xy format images are not something you should be using at all; they were

Re: xf86 input driver API question

On Sun, May 14, 2017 at 05:48:08PM +0200, Martin Kepplinger wrote: > might be a dumb question, but I don't find resources: If an Xorg input > driver supports GET_ABI_MAJOR() < 14, what exactly does that mean? > xserver < 1.14 is supported? Where is the documentation on this driver ABI? the ABI is

Re: [PATCH xkeyboard-config] Add evdev mappings for KEY_SOUND, KEY_UWB, KEY_WWAN and KEY_RFKILL

adding svu to CC: On Fri, May 12, 2017 at 04:18:42PM +0200, Hans de Goede wrote: > KEY_SOUND, KEY_WWAN and KEY_RFKILL are used on actual devices and > current xproto master defines keysyms for these. Add mappings for > these keys. > > The XF86UWB keysm exists for quite a while now, as does the

xf86 input driver API question

might be a dumb question, but I don't find resources: If an Xorg input driver supports GET_ABI_MAJOR() < 14, what exactly does that mean? xserver < 1.14 is supported? Where is the documentation on this driver ABI? thanks martin

Re: xf86 input driver API question

On 05/14/17 08:48 AM, Martin Kepplinger wrote: might be a dumb question, but I don't find resources: If an Xorg input driver supports GET_ABI_MAJOR() < 14, what exactly does that mean? xserver < 1.14 is supported? Where is the documentation on this driver ABI? It's out of date, but