> Why are pointer cursors misplaced on paravirtualized drivers?
>
> It is because the paravirtualized drivers or VM viewers do *not* place
> the cursor plane at the CRTC_X, CRTC_Y position in the guest CRTC area.
> This is obvious: if CRTC_X, CRTC_Y were honoured, there would be no
> misplacement.
> On Jun 3, 2022, at 10:14 AM, Simon Ser wrote:
>
> Hi,
>
> Please, read this thread:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Farchives%2Fdri-devel%2F2020-March%2Fthread.html%23259615&data=05%7C01%7Czackr%40vmware.com%7C05141cb812004e947f0408da
On Jun 3, 2022, at 10:56 AM, Simon Ser
mailto:cont...@emersion.fr>> wrote:
⚠ External Email
On Friday, June 3rd, 2022 at 16:38, Zack Rusin
mailto:za...@vmware.com>> wrote:
On Jun 3, 2022, at 10:32 AM, Simon Ser
mailto:cont...@emersion.fr>> wrote:
⚠ External Email
On Friday, June 3rd, 2022
On Jun 3, 2022, at 11:22 AM, Simon Ser
mailto:cont...@emersion.fr>> wrote:
⚠ External Email
On Friday, June 3rd, 2022 at 17:17, Zack Rusin
mailto:za...@vmware.com>> wrote:
On Jun 3, 2022, at 10:56 AM, Simon Ser
mailto:cont...@emersion.fr>> wrote:
⚠ External Email
On Friday, June 3rd, 2022
> On Jun 3, 2022, at 10:32 AM, Simon Ser wrote:
>
> ⚠ External Email
>
> On Friday, June 3rd, 2022 at 16:27, Zack Rusin wrote:
>
>>> In particular: since the driver will ignore the KMS cursor plane
>>> position set by user-space, I don't think it's okay to just expose
>>> without opt-in from
On Jun 3, 2022, at 11:49 AM, Simon Ser
mailto:cont...@emersion.fr>> wrote:
⚠ External Email
On Friday, June 3rd, 2022 at 17:32, Zack Rusin
mailto:za...@vmware.com>> wrote:
On Jun 3, 2022, at 11:22 AM, Simon Ser
mailto:cont...@emersion.fr>> wrote:
⚠ External Email
On Friday, June 3rd, 2022
> On Jun 5, 2022, at 3:30 AM, Simon Ser wrote:
>
> ⚠ External Email
>
> On Friday, June 3rd, 2022 at 20:31, Zack Rusin wrote:
>
>>> My proposal was:
>>>
>>> - Introduce DRM_CLIENT_CAP_CURSOR_PLANE_NO_POSITION (or a better name).
>>> Only
>>> user-space which supports th
Hi,
> I don’t think I see how that fixes anything. In particular I don’t see
> a way of fixing the old user space at all. We require hotspot info,
> old user space doesn’t set it because there’s no way of setting it on
> atomic kms. Whether we expose cursor plane or not doesn’t change the
> fact
> On Jun 5, 2022, at 12:26 PM, Simon Ser wrote:
>
> --- Original Message ---
> On Sunday, June 5th, 2022 at 17:47, Zack Rusin wrote:
>
Also, let me point this out because it also seems to be a fundamental
misunderstanding, user space implementing software cursor doesn’t fix
>
On Tue, 2022-06-07 at 11:07 +0300, Pekka Paalanen wrote:
> On Fri, 03 Jun 2022 14:14:59 +
> Simon Ser wrote:
>
> > Hi,
> >
> > Please, read this thread:
> > https://lists.freedesktop.org/archives/dri-devel/2020-March/thread.html#259615
> >
> > It has a lot of information about the pitfalls
Hi,
> > Typically there is a communication path from guest to host for pointer
> > movements (i.e. crtc_x + crtc_y updates), so the host knows where the
> > guest wants the cursor plane being placed. So in case the pointer is
> > moved by other means (different input device, some application wa
Alexandros Frantzis (2):
client: Document best practices for event queue changes
client: Lock display when setting a proxy event queue
Antonin Décimo (1):
Check that XDG base directories paths are absolute
Simon Ser (13):
cursor: remove xcursor_file_load_images wrapper
On Wed, 2022-06-08 at 10:53 +0300, Pekka Paalanen wrote:
> On Tue, 7 Jun 2022 17:50:24 +
> Zack Rusin wrote:
>
> > On Tue, 2022-06-07 at 11:07 +0300, Pekka Paalanen wrote:
> > > On Fri, 03 Jun 2022 14:14:59 +
> > > Simon Ser wrote:
> > >
> > > > Hi,
> > > >
> > > > Please, read this
13 matches
Mail list logo
