Re: [PATCH xserver 1/3] xfree86: Immediately handle failure to set HW cursor, v5

Hi, On 05-12-16 10:25, Michael Thayer wrote: Hello Hans, Polite ping on this one. I've already given this series my: Reviewed-by: Hans de Goede There is not much else I can do, from here on it is up to the xserver maintainers to pick up the series. Regards, Hans

Re: [PATCH xserver 1/3] xfree86: Immediately handle failure to set HW cursor, v5

Hello Hans, Polite ping on this one. Regards and thanks Michael 01.10.2016 12:01, Hans de Goede wrote: Hi, On 30-09-16 17:55, Michael Thayer wrote: Based on v4 by Alexandre Courbot There is currently no reliable way to report failure to set a HW cursor. Still such

Re: [PATCH xserver 1/3] xfree86: Immediately handle failure to set HW cursor, v5

Hello Adam, On 05.10.2016 21:33, Adam Jackson wrote: On Fri, 2016-09-30 at 17:55 +0200, Michael Thayer wrote: v5: Updated the patch to apply to current git HEAD, split up into two patches (server and modesetting driver) and adjusted the code slightly to match surrounding code. I also

Re: [PATCH xserver 1/3] xfree86: Immediately handle failure to set HW cursor, v5

On Fri, 2016-09-30 at 17:55 +0200, Michael Thayer wrote: > > > v5: Updated the patch to apply to current git HEAD, split up into two > patches (server and modesetting driver) and adjusted the code slightly > to match surrounding code.  I also removed the new exported function >

Re: [PATCH xserver 1/3] xfree86: Immediately handle failure to set HW cursor, v5

Hi, On 30-09-16 17:55, Michael Thayer wrote: Based on v4 by Alexandre Courbot There is currently no reliable way to report failure to set a HW cursor. Still such failures can happen if e.g. the MODE_CURSOR DRM ioctl fails (which currently happens at least with modesetting

[PATCH xserver 1/3] xfree86: Immediately handle failure to set HW cursor, v5

Based on v4 by Alexandre Courbot There is currently no reliable way to report failure to set a HW cursor. Still such failures can happen if e.g. the MODE_CURSOR DRM ioctl fails (which currently happens at least with modesetting on Tegra for format incompatibility reasons).