(In reply to comment #11)
> [...] I haven't had the mouse corruption issue on this patched driver, and the
> message appears in dmesg:
Okay, so an unpatched driver probably would use too large offsets sometimes, which would definitely explain the corrupted cursor. So the fix seems to be working.
> I have to say that the log confuses me since 1 << 27 is not 0.
Indeed, but that's just a bug of the DRM_INFO call. :) (Type mismatch between format string and values)
I'm attaching the fix as I submitted it for inclusion into the kernel.
Created attachment 58436
Submitted fix
(In reply to comment #11)
> [...] I haven't had the mouse corruption issue on this patched driver, and the
> message appears in dmesg:
Okay, so an unpatched driver probably would use too large offsets sometimes, which would definitely explain the corrupted cursor. So the fix seems to be working.
> I have to say that the log confuses me since 1 << 27 is not 0.
Indeed, but that's just a bug of the DRM_INFO call. :) (Type mismatch between format string and values)
I'm attaching the fix as I submitted it for inclusion into the kernel.