[adding Zack Rusin again who seems to have fallen from the Cc list]
Albert Esteve 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
Zack Rusin writes:
[adding Aleix Pol from KDE/kwin to Cc list]
Hello Zack,
> On Wed, 2023-06-21 at 09:10 +0200, Javier Martinez Canillas wrote:
[...]
>> >
>> > Hi all,
>> >
>> > We have been testing the v2 of this patch and it works correctly for us.
>> >
>> > First we tested with a patche
On Wed, 2023-06-21 at 09:10 +0200, Javier Martinez Canillas wrote:
> !! External Email
>
> [adding Zack Rusin again who seems to have fallen from the Cc list]
>
> Albert Esteve writes:
> > On 6/10/22 10:59, Daniel Vetter wrote:
> > > On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
On 6/10/22 10:59, Daniel Vetter wrote:
On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
Hi all,
Kinda top post because the thread is sprawling and I think we need a
summary/restart. I think there's at least 3 issues here:
- lack of hotspot property support, which means composit
Hi,
On Tue, 14 Jun 2022 at 15:40, Zack Rusin wrote:
> On Tue, 2022-06-14 at 10:36 +0300, Pekka Paalanen wrote:
> > The reason I am saying that you need to fix other issues with
> > virtualized drivers at the same time is because those other issues are
> > the sole and only reason why the driver w
On Tue, 2022-06-14 at 10:36 +0300, Pekka Paalanen wrote:
> On Mon, 13 Jun 2022 14:54:57 +
> Zack Rusin wrote:
>
> > On Mon, 2022-06-13 at 17:25 +0300, Pekka Paalanen wrote:
> > > On Mon, 13 Jun 2022 13:14:48 +
> > > Zack Rusin wrote:
> > >
> > > > On Mon, 2022-06-13 at 10:33 +0300, Pe
On Mon, 13 Jun 2022 14:54:57 +
Zack Rusin wrote:
> On Mon, 2022-06-13 at 17:25 +0300, Pekka Paalanen wrote:
> > On Mon, 13 Jun 2022 13:14:48 +
> > Zack Rusin wrote:
> >
> > > On Mon, 2022-06-13 at 10:33 +0300, Pekka Paalanen wrote:
> > > > On Fri, 10 Jun 2022 14:24:01 +
> > > >
On Mon, 2022-06-13 at 17:25 +0300, Pekka Paalanen wrote:
> On Mon, 13 Jun 2022 13:14:48 +
> Zack Rusin wrote:
>
> > On Mon, 2022-06-13 at 10:33 +0300, Pekka Paalanen wrote:
> > > On Fri, 10 Jun 2022 14:24:01 +
> > > Zack Rusin wrote:
> > >
> > > > On Fri, 2022-06-10 at 10:59 +0200, Da
On Mon, 13 Jun 2022 13:14:48 +
Zack Rusin wrote:
> On Mon, 2022-06-13 at 10:33 +0300, Pekka Paalanen wrote:
> > On Fri, 10 Jun 2022 14:24:01 +
> > Zack Rusin wrote:
> >
> > > On Fri, 2022-06-10 at 10:59 +0200, Daniel Vetter wrote:
> > > > ⚠ External Email
> > > >
> > > > On Fri, Ju
On Mon, 2022-06-13 at 10:33 +0300, Pekka Paalanen wrote:
> On Fri, 10 Jun 2022 14:24:01 +
> Zack Rusin wrote:
>
> > On Fri, 2022-06-10 at 10:59 +0200, Daniel Vetter wrote:
> > > ⚠ External Email
> > >
> > > On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
> > > > Hi all,
> >
On Sat, 11 Jun 2022 17:34:50 +0200
Hans de Goede wrote:
> Hi,
>
> On 6/10/22 14:53, Simon Ser wrote:
> > On Friday, June 10th, 2022 at 14:36, Gerd Hoffmann
> > wrote:
> >
> >> Hi,
> >>
> As Pekka mentionned, I'd also like to have a conversation of how far we
> want to
> pu
On Fri, 10 Jun 2022 14:24:01 +
Zack Rusin wrote:
> On Fri, 2022-06-10 at 10:59 +0200, Daniel Vetter wrote:
> > ⚠ External Email
> >
> > On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
> > > Hi all,
> > >
> > > Kinda top post because the thread is sprawling and I think we ne
Hi,
On 6/10/22 14:53, Simon Ser wrote:
> On Friday, June 10th, 2022 at 14:36, Gerd Hoffmann wrote:
>
>> Hi,
>>
As Pekka mentionned, I'd also like to have a conversation of how far we
want to
push virtualized driver features. I think KMS support is a good feature to
have
>>>
On Fri, 2022-06-10 at 10:59 +0200, Daniel Vetter wrote:
> ⚠ External Email
>
> On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
> > Hi all,
> >
> > Kinda top post because the thread is sprawling and I think we need a
> > summary/restart. I think there's at least 3 issues here:
> >
On Friday, June 10th, 2022 at 14:36, Gerd Hoffmann wrote:
> Hi,
>
> > > As Pekka mentionned, I'd also like to have a conversation of how far we
> > > want to
> > > push virtualized driver features. I think KMS support is a good feature
> > > to have
> > > to spin up a VM and have all of the bas
Hi,
> > As Pekka mentionned, I'd also like to have a conversation of how far we
> > want to
> > push virtualized driver features. I think KMS support is a good feature to
> > have
> > to spin up a VM and have all of the basics working. However I don't think
> > it's
> > a good idea to try to
Hi,
> > 4. make sure the hotspot property is only set on VIRTUAL_CURSOR planes
> > and nothing else in the rebased patch series
>
> Simon also mentioned on irc that these special planes must not expose the
> CRTC_X/Y property, since that doesn't really do much at all. Or is our
> understand
On Fri, Jun 10, 2022 at 09:15:35AM +, Simon Ser wrote:
> On Friday, June 10th, 2022 at 10:41, Daniel Vetter wrote:
>
> > Anything I've missed? Or got completely wrong?
>
> This plan looks good to me.
>
> As Pekka mentionned, I'd also like to have a conversation of how far we want
> to
> pu
On Friday, June 10th, 2022 at 10:41, Daniel Vetter wrote:
> Anything I've missed? Or got completely wrong?
This plan looks good to me.
As Pekka mentionned, I'd also like to have a conversation of how far we want to
push virtualized driver features. I think KMS support is a good feature to have
On Fri, Jun 10, 2022 at 08:54:03AM +, Simon Ser wrote:
> I agree with what others have replied, just adding a few more details.
>
> On Thursday, June 9th, 2022 at 21:39, Zack Rusin wrote:
>
> > virtualized drivers send drm_kms_helper_hotplug_event which sends a
> > HOTPLUG=1
> > event with
On Fri, Jun 10, 2022 at 10:41:05AM +0200, Daniel Vetter wrote:
> Hi all,
>
> Kinda top post because the thread is sprawling and I think we need a
> summary/restart. I think there's at least 3 issues here:
>
> - lack of hotspot property support, which means compositors can't really
> support hot
On Fri, 10 Jun 2022 10:41:05 +0200
Daniel Vetter wrote:
> Hi all,
>
> Kinda top post because the thread is sprawling and I think we need a
> summary/restart. I think there's at least 3 issues here:
>
> - lack of hotspot property support, which means compositors can't really
> support hotspot
I agree with what others have replied, just adding a few more details.
On Thursday, June 9th, 2022 at 21:39, Zack Rusin 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" prope
Hi all,
Kinda top post because the thread is sprawling and I think we need a
summary/restart. I think there's at least 3 issues here:
- lack of hotspot property support, which means compositors can't really
support hotspot with atomic. Which isn't entirely true, because you
totally can use at
On Fri, Jun 10, 2022 at 10:49:31AM +0300, Pekka Paalanen wrote:
> On Thu, 9 Jun 2022 19:39:39 +
> Zack Rusin wrote:
>
> > 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 +030
On Thu, 9 Jun 2022 19:39:39 +
Zack Rusin wrote:
> 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 +
> > > > Si
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
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
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
> 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
>
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 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
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 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: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: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 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
> 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 Tue, 7 Jun 2022 16:30:23 +0200
Gerd Hoffmann wrote:
> > 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:
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 thread:
> > > https://lists.freedesktop.org/archives/dri-devel/2020-March/thr
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 of cursor hotspot and
> other things done by VM software.
>
> In particula
On Fri, 3 Jun 2022 14:38:54 +
Zack Rusin wrote:
> > 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
On Sunday, June 5th, 2022 at 20:16, Zack Rusin wrote:
> > At any rate, I consider broken any driver which exposes a cursor plane,
> > then doesn't display it exactly at the CRTC_X/CRTC_Y
>
> But we do… The cursor is at crtc_x, crtc_y.
How do you show the cursor on the host side then? Pretty sure
--- 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
> > > anything. Just leaves everything broken in dif
On Saturday, June 4th, 2022 at 23:19, Hans de Goede wrote:
> >>> My proposal was:
> >>>
> >>> - Introduce DRM_CLIENT_CAP_CURSOR_PLANE_NO_POSITION (or a better name).
> >>> Only
> >>> user-space which supports the hotspot props will enable it.
> >>> - By default, don't expose a cursor plane, beca
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 the hotspot props will enable it.
> > > > > > - By default, do
Hi,
On 6/3/22 17:22, Simon Ser wrote:
> On Friday, June 3rd, 2022 at 17:17, Zack Rusin wrote:
>
>>
>>> On Jun 3, 2022, at 10:56 AM, Simon Ser wrote:
>>> ⚠ External Email
>>>
>>> On Friday, June 3rd, 2022 at 16:38, Zack Rusin wrote:
>>>
> On Jun 3, 2022, at 10:32 AM, Simon Ser wrote:
>
On Friday, June 3rd, 2022 at 17:32, Zack Rusin wrote:
> > On Jun 3, 2022, at 11:22 AM, Simon Ser wrote:
> > ⚠ External Email
> >
> > On Friday, June 3rd, 2022 at 17:17, Zack Rusin wrote:
> >
> >
> > >
> > >
> > > > On Jun 3, 2022, at 10:56 AM, Simon Ser wrote:
> > > > ⚠ External Email
> > >
On Friday, June 3rd, 2022 at 17:17, Zack Rusin wrote:
>
> > On Jun 3, 2022, at 10:56 AM, Simon Ser wrote:
> > ⚠ External Email
> >
> > On Friday, June 3rd, 2022 at 16:38, Zack Rusin wrote:
> >
> > > > On Jun 3, 2022, at 10:32 AM, Simon Ser wrote:
> > > >
> > > > ⚠ External Email
> > > >
> > >
On Friday, June 3rd, 2022 at 16:38, Zack Rusin wrote:
> > 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-sp
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 user-space (e.g. with a DRM_CLIENT_CAP).
> >
> > cc wayland-devel and Pekka for
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 of cursor hotspot and
other things done by VM software.
In particular: since the driver will ignore the KMS cursor plane
position set by use
52 matches
Mail list logo
