From: Simon Ser <contact@emersion.fr>
To: Zack Rusin <zackr@vmware.com>
Cc: "hdegoede@redhat.com" <hdegoede@redhat.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"gurchetansingh@chromium.org" <gurchetansingh@chromium.org>,
Martin Krastev <krastevm@vmware.com>,
"ppaalanen@gmail.com" <ppaalanen@gmail.com>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"wayland-devel@lists.freedesktop.org"
<wayland-devel@lists.freedesktop.org>,
Maaz Mombasawala <mombasawalam@vmware.com>
Subject: Re: [PATCH 0/6] drm: Add mouse cursor hotspot support to atomic KMS
Date: Fri, 10 Jun 2022 08:54:03 +0000 [thread overview]
Message-ID: <4CJ-x-v-p82cgfBong1zaXjiyI_CnIyh2mOHdGEDi8dpNgr-M4cagtnxFnFCipfM9OjcoM9ZtWtaHKglAzjDzP8169AKwGqGMVT042UhHXk=@emersion.fr> (raw)
In-Reply-To: <0485fdf9844f8c89cd5670096b78f8090378b2a1.camel@vmware.com>
I agree with what others have replied, just adding a few more details.
On Thursday, June 9th, 2022 at 21:39, Zack Rusin <zackr@vmware.com> wrote:
> virtualized drivers send drm_kms_helper_hotplug_event which sends a HOTPLUG=1
> event with a changed preferred width/height
(Note: and the "hotplug_mode_update" property is set to 1.)
> suggested_x and suggested_y properties
These come with their own set of issues. They are poorly defined, but it seems
like they describe a position in physical pixel coordinates. Compositors don't
use physical pixel coordinates to organize their outputs, instead they use
logical coordinates. For instance, a HiDPI 4k screen with a scale of 2 will
take up 1920x1080 logical pixels. There is no way to convert physical pixel
coordinates to logical pixel coordinates in the general case, because there's
no "global scale factor". So suggested_x/y are incompatible with the way
compositors work.
next prev parent reply other threads:[~2022-06-10 8:54 UTC|newest]
Thread overview: 64+ 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 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 [this message]
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
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='4CJ-x-v-p82cgfBong1zaXjiyI_CnIyh2mOHdGEDi8dpNgr-M4cagtnxFnFCipfM9OjcoM9ZtWtaHKglAzjDzP8169AKwGqGMVT042UhHXk=@emersion.fr' \
--to=contact@emersion.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).