https://bugs.kde.org/show_bug.cgi?id=449331
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xaver.h...@gmail.com
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #6 from Zamundaaa <xaver.h...@gmail.com> ---
With legacy functions the hotspot only works because we pass it into
drmModeSetCursor2 (which is a workaround for limitations in v1 of
drmModeSetCursor) - with AMS the VM has absolutely no information about what we
use the cursor plane for, or what the hotspot is. It assuming that we display
the cursor in the cursor plane is also a hack and could cause more breakage
soon.
To solve this problem either VMs need to stop making such assumptions and/or
some new drm properties would need to be introduced that signal whether or not
a plane is used at all for the cursor and if so, what the cursor hotspot is
supposed to be.
--
You are receiving this mail because:
You are watching all bug changes.
