From: Javier Martinez Canillas <javierm@redhat.com>
To: Zack Rusin <zackr@vmware.com>, Albert Esteve <aesteve@redhat.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
krastevm@vmware.com, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Gurchetan Singh <gurchetansingh@chromium.org>,
Hans de Goede <hdegoede@redhat.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>,
wayland-devel <wayland-devel@lists.freedesktop.org>,
mombasawalam@vmware.com
Subject: Re: [PATCH 0/6] drm: Add mouse cursor hotspot support to atomic KMS
Date: Wed, 21 Jun 2023 09:10:24 +0200 [thread overview]
Message-ID: <87legdi93z.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <3ef205a7-f418-e22d-6bae-7be08f60d2f8@redhat.com>
[adding Zack Rusin again who seems to have fallen from the Cc list]
Albert Esteve <aesteve@redhat.com> writes:
> On 6/10/22 10:59, Daniel Vetter wrote:
>> On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
[...]
>>> - third issue: These special virtual display properties arent documented.
>>> Aside from hotspot there's also suggested X/Y and maybe other stuff. I
>>> have no idea what suggested X/Y does and what userspace should do with
>>> it. I think we need a new section for virtualized drivers which:
>>> - documents all the properties involved
>>> - documents the new cap for enabling virtual cursor planes
>>> - documents some of the key flows that compositors should implement for
>>> best experience
>>> - documents how exactly the user experience will degrade if compositors
>>> pretend it's just a normal kms driver (maybe put that into each of the
>>> special flows that a compositor ideally supports)
>>> - whatever other comments and gaps I've missed, I'm sure
>>> Simon/Pekka/others will chime in once the patch exists.
What is missing for these patches to land? If I understood correctly is
just these properties documentation that Sima asked above ?
>> Great bonus would be an igt which demonstrates these flows. With the
>> interactive debug breakpoints to wait for resizing or whatever this should
>> be all neatly possible.
>> -Daniel
>
> Hi all,
>
> We have been testing the v2 of this patch and it works correctly for us.
>
> First we tested with a patched Mutter, the mouse clicks were correct,
> and behavior was as expected.
>
> But I've also added an IGT test as suggested above:
> https://gitlab.freedesktop.org/aesteve/igt-gpu-tools/-/compare/master...modeset-cursor-hotspot-test?from_project_id=1274
>
> I could post the IGT patch upstream once Zack's patches land.
>
Zack, are you planning to re-spin the series soon? Otherwise Albert could
continue working on that if you prefer.
> Hope that helps!
>
> -Albert
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-06-21 7:10 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:42 [PATCH 0/6] drm: Add mouse cursor hotspot support to atomic KMS Zack Rusin
2022-06-02 15:42 ` [PATCH 1/6] drm/atomic: Add support for mouse hotspots Zack Rusin
2022-06-02 15:42 ` [PATCH 2/6] drm/vmwgfx: Create mouse hotspot properties on cursor planes Zack Rusin
2022-06-03 13:11 ` Martin Krastev (VMware)
2022-06-02 15:42 ` [PATCH 3/6] drm/qxl: " Zack Rusin
2022-06-02 22:05 ` kernel test robot
2022-06-02 22:05 ` kernel test robot
2022-06-02 23:26 ` kernel test robot
2022-06-02 23:26 ` kernel test robot
2022-06-02 23:26 ` kernel test robot
2022-06-02 15:42 ` [PATCH 4/6] drm/vboxvideo: " Zack Rusin
2022-06-02 15:42 ` [PATCH 5/6] drm/virtio: " Zack Rusin
2022-06-02 15:42 ` [PATCH 6/6] drm: Remove legacy cursor hotspot code Zack Rusin
2022-06-03 10:28 ` [PATCH 0/6] drm: Add mouse cursor hotspot support to atomic KMS Gerd Hoffmann
2022-06-03 14:43 ` Zack Rusin
2022-06-03 14:14 ` Simon Ser
2022-06-03 14:27 ` Zack Rusin
2022-06-03 14:32 ` Simon Ser
2022-06-03 14:38 ` Zack Rusin
2022-06-03 14:56 ` Simon Ser
2022-06-03 15:17 ` Zack Rusin
2022-06-03 15:22 ` Simon Ser
2022-06-03 15:32 ` Zack Rusin
2022-06-03 15:49 ` Simon Ser
2022-06-03 18:31 ` Zack Rusin
2022-06-05 7:30 ` Simon Ser
2022-06-05 15:47 ` Zack Rusin
2022-06-05 16:26 ` Simon Ser
2022-06-05 18:16 ` Zack Rusin
2022-06-06 8:11 ` Simon Ser
2022-06-04 21:19 ` Hans de Goede
2022-06-05 7:34 ` Simon Ser
2022-06-07 11:25 ` Gerd Hoffmann
2022-06-06 9:13 ` Pekka Paalanen
2022-06-07 8:07 ` Pekka Paalanen
2022-06-07 14:30 ` Gerd Hoffmann
2022-06-08 7:53 ` Pekka Paalanen
2022-06-08 14:52 ` Gerd Hoffmann
2022-06-07 17:50 ` Zack Rusin
2022-06-08 7:53 ` Pekka Paalanen
2022-06-09 19:39 ` Zack Rusin
2022-06-10 7:49 ` Pekka Paalanen
2022-06-10 8:22 ` Jonas Ådahl
2022-06-10 8:54 ` Simon Ser
2022-06-10 9:01 ` Daniel Vetter
2022-06-10 8:41 ` Daniel Vetter
2022-06-10 8:56 ` Pekka Paalanen
2022-06-10 8:59 ` Daniel Vetter
2022-06-10 12:03 ` Gerd Hoffmann
2022-06-10 14:24 ` Zack Rusin
2022-06-13 7:33 ` Pekka Paalanen
2022-06-13 13:14 ` Zack Rusin
2022-06-13 14:25 ` Pekka Paalanen
2022-06-13 14:54 ` Zack Rusin
2022-06-14 7:36 ` Pekka Paalanen
2022-06-14 14:40 ` Zack Rusin
2022-06-14 14:54 ` Daniel Stone
2023-06-09 15:20 ` Albert Esteve
2023-06-21 7:10 ` Javier Martinez Canillas [this message]
2023-06-22 4:29 ` Zack Rusin
2023-06-22 6:20 ` Javier Martinez Canillas
2022-06-10 9:15 ` Simon Ser
2022-06-10 9:49 ` Daniel Vetter
2022-06-10 12:36 ` Gerd Hoffmann
2022-06-10 12:53 ` Simon Ser
2022-06-11 15:34 ` Hans de Goede
2022-06-13 7:45 ` Pekka Paalanen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87legdi93z.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=aesteve@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=hdegoede@redhat.com \
--cc=krastevm@vmware.com \
--cc=kraxel@redhat.com \
--cc=mombasawalam@vmware.com \
--cc=ppaalanen@gmail.com \
--cc=tzimmermann@suse.de \
--cc=wayland-devel@lists.freedesktop.org \
--cc=zackr@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.