From: Pekka Paalanen <ppaalanen@gmail.com>
To: Michael Banack <banackm@vmware.com>
Cc: "mripard@kernel.org" <mripard@kernel.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"javierm@redhat.com" <javierm@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Martin Krastev <krastevm@vmware.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
Ian Forbes <iforbes@vmware.com>,
Maaz Mombasawala <mombasawalam@vmware.com>,
"zack@kde.org" <zack@kde.org>
Subject: Re: [PATCH v4 2/8] drm/atomic: Add support for mouse hotspots
Date: Tue, 11 Jul 2023 10:14:42 +0300 [thread overview]
Message-ID: <20230711101442.72530df5@eldfell> (raw)
In-Reply-To: <9768c00d-536b-dd7b-c8e2-e9d920cd6959@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Mon, 10 Jul 2023 10:46:56 -0700
Michael Banack <banackm@vmware.com> wrote:
> On 7/10/23 01:17, Pekka Paalanen wrote:
> > On Fri, 7 Jul 2023 13:54:21 -0700
> > Michael Banack <banackm@vmware.com> wrote:
...
> >> So I guess I would vote for trying to include something to that effect
> >> as context or explanation, but not try to strictly define how that works?
> > Yes, exactly.
>
> Okay, if we can keep the mouse/input stuff on the fuzzy side then I
> think we're on the same page.
Very much of the fuzzy side, yes! All I am saying is that one cannot
explain the hotspot property without saying anything about it being
connected with input devices in some way. The very key I want to see
documented is that all cursor-needing pointing input devices and all
KMS cursor planes exposed to the guest OS are meant to be associated
with the same single conceptual pointer. That is all.
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-11 7:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 5:21 [PATCH v4 0/8] Fix cursor planes with virtualized drivers Zack Rusin
2023-06-28 5:21 ` [PATCH v4 1/8] drm: Disable the cursor plane on atomic contexts " Zack Rusin
2023-06-28 5:21 ` [PATCH v4 2/8] drm/atomic: Add support for mouse hotspots Zack Rusin
2023-06-28 7:41 ` Pekka Paalanen
2023-06-28 7:54 ` Pekka Paalanen
2023-06-28 8:30 ` Javier Martinez Canillas
2023-06-28 19:54 ` Zack Rusin
2023-06-29 8:03 ` Pekka Paalanen
2023-07-03 21:06 ` Michael Banack
2023-07-04 8:08 ` Pekka Paalanen
2023-07-05 16:08 ` Michael Banack
2023-07-06 8:01 ` Pekka Paalanen
2023-07-06 16:23 ` Michael Banack
2023-07-07 8:38 ` Pekka Paalanen
2023-07-07 20:54 ` Michael Banack
2023-07-10 8:17 ` Pekka Paalanen
2023-07-10 17:46 ` Michael Banack
2023-07-11 7:14 ` Pekka Paalanen [this message]
2023-07-18 8:41 ` Javier Martinez Canillas
2023-07-18 9:27 ` Javier Martinez Canillas
2023-07-18 9:56 ` Pekka Paalanen
2023-06-28 14:15 ` Simon Ser
2023-06-28 16:26 ` Zack Rusin
2023-06-29 8:16 ` Pekka Paalanen
2023-07-03 21:15 ` Michael Banack
2023-06-28 5:21 ` [PATCH v4 3/8] drm/vmwgfx: Use the hotspot properties from cursor planes Zack Rusin
2023-06-28 5:21 ` [PATCH v4 4/8] drm/qxl: " Zack Rusin
2023-06-28 5:21 ` [PATCH v4 5/8] drm/vboxvideo: " Zack Rusin
2023-06-28 5:21 ` [PATCH v4 6/8] drm/virtio: " Zack Rusin
2023-06-28 5:21 ` [PATCH v4 7/8] drm: Remove legacy cursor hotspot code Zack Rusin
2023-06-28 5:21 ` [PATCH v4 8/8] drm: Introduce DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT Zack Rusin
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=20230711101442.72530df5@eldfell \
--to=ppaalanen@gmail.com \
--cc=airlied@linux.ie \
--cc=banackm@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iforbes@vmware.com \
--cc=javierm@redhat.com \
--cc=krastevm@vmware.com \
--cc=mombasawalam@vmware.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
--cc=zack@kde.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox