>>
>>
>> -Original Message-
>> From: Hoosier, Matt
>> Sent: Monday, June 17, 2024 8:28 AM
>> To: Pekka Paalanen
>> Cc: 'Marius Vlad' ;
>> 'wayland-devel@lists.freedesktop.org' ;
>> 'Daniel Stone'
&
> -Original Message-
> From: Pekka Paalanen
> Sent: Monday, June 17, 2024 3:28 AM
> To: Hoosier, Matt
> Cc: 's...@cmpwn.com' ; 'cont...@emersion.fr'
> ; 'Marius Vlad' ;
> 'wayland-devel@lists.freedesktop.org' de...@lists.free
> -Original Message-
> From: Pekka Paalanen
> Sent: Thursday, June 13, 2024 3:32 AM
> To: Hoosier, Matt
> Cc: 's...@cmpwn.com' ; 'cont...@emersion.fr'
> ; 'Marius Vlad' ;
> 'wayland-devel@lists.freedesktop.org' de...@lists
> -Original Message-
> From: Hoosier, Matt
> Sent: Wednesday, June 12, 2024 8:37 AM
> To: Pekka Paalanen
> Cc: s...@cmpwn.com; cont...@emersion.fr; Marius Vlad
> ; wayland-devel@lists.freedesktop.org; Daniel
> Stone
> Subject: RE: Full-motion zero-copy
> -Original Message-
> From: Pekka Paalanen
> Sent: Wednesday, June 12, 2024 4:03 AM
> To: Hoosier, Matt
> Cc: s...@cmpwn.com; cont...@emersion.fr; Marius Vlad
> ; wayland-devel@lists.freedesktop.org; Daniel
> Stone
> Subject: Re: Full-motion zero-copy screen c
ing
renderbuffer, then the mirror-of relationship continues as with MR 1476 just to
invoke an explicit weston_renderer pass to draw the correct logical contents.
How does this strike you?
-Matt
> -Original Message-
> From: Pekka Paalanen
> Sent: Monday, June 10, 2024 3:03 AM
>
7, 2024 10:17 AM
To: Hoosier, Matt
Cc: Pekka Paalanen ; Marius Vlad
; wayland-devel@lists.freedesktop.org
Subject: Re: Ways to test Weston during development (Re: Full-motion zero-copy
screen capture in Weston)
Hi Matt, On Fri, 7 Jun 2024 at 15: 30, Hoosier, Matt wrote: > Would Meso
…) manually. I wonder why Meson wrapping was not used for this?
-Matt
From: Hoosier, Matt
Sent: Wednesday, June 5, 2024 7:44 AM
To: Daniel Stone ; Pekka Paalanen
Cc: s...@cmpwn.com; cont...@emersion.fr; Marius Vlad
; wayland-devel@lists.freedesktop.org
Subject: Re: Ways to test Weston during development
.paala...@collabora.com>> wrote:
On Fri, 31 May 2024 13:26:12 +
"Hoosier, Matt" mailto:matt.hoos...@garmin.com>>
wrote:
>
> My goal is to implement this screen capture with a guarantee that the
> copy comes from a KMS writeback connector. I know this sounds
enter
…
user@toolbox:~$ sudo ln -s /run/host/run/seatd.socket /run/
user@toolbox:~$ weston --backend=drm
-Matt
From: Daniel Stone
Date: Wednesday, June 5, 2024 at 5:07 AM
To: Pekka Paalanen
Cc: "Hoosier, Matt" , "s...@cmpwn.com"
, "cont...@emersion.fr" ,
--Original Message-
> From: Pekka Paalanen
> Sent: Tuesday, June 4, 2024 3:20 AM
> To: Hoosier, Matt
> Cc: s...@cmpwn.com; cont...@emersion.fr; Marius Vlad
> ; wayland-devel@lists.freedesktop.org
> Subject: Re: Full-motion zero-copy screen capture in Weston
>
> On Mon, 3 Jun 20
ius linked
earlier.
On 6/3/24, 3:54 AM, "Pekka Paalanen" mailto:pekka.paala...@collabora.com>> wrote:
On Fri, 31 May 2024 13:26:12 +
"Hoosier, Matt" mailto:matt.hoos...@garmin.com>>
wrote:
>
> My goal is to implement this screen capture with a gua
starting point.
-Matt
From: Simon Ser
Date: Friday, May 31, 2024 at 10:16 AM
To: Andri Yngvason
Cc: "Hoosier, Matt" , Pekka Paalanen
, "s...@cmpwn.com" , Marius Vlad
, "wayland-devel@lists.freedesktop.org"
Subject: Re: Full-motion zero-copy screen capture in Weston
lip. Having the compositor manage the buffers' lifetimes and just publishing
out handles (in the style of those two wlr extensions) to those probably fits
better.
-Matt
From: Pekka Paalanen
Sent: Friday, May 31, 2024 3:02 AM
To: Hoosier, Matt
Cc: Marius
in the compositor's Pixman backend and/or a client who
wants to map it to the CPU upon delivery.
-Matt
On 5/30/24, 3:22 AM, "Pekka Paalanen" mailto:pekka.paala...@collabora.com>> wrote:
On Wed, 29 May 2024 15:18:16 +
"Hoosier, Matt" mailto:matt.hoos...@garmin.
sktop session somewhat implies the
compositor is driving the physical hardware?
> -Original Message-
> From: Pekka Paalanen
> Sent: Wednesday, May 29, 2024 2:43 AM
> To: Marius Vlad ; Hoosier, Matt
>
> Cc: wayland-devel@lists.freedesktop.org
> Subject: Re: Full-motion z
: Saturday, May 25, 2024 6:12 AM
> To: Hoosier, Matt
> Cc: wayland-devel@lists.freedesktop.org
> Subject: Re: Full-motion zero-copy screen capture in Weston
>
> On Fri, May 24, 2024 at 09:43:58PM +, Hoosier, Matt wrote:
> > Hi,
> >
> > I'm interested in fi
Hi,
I'm interested in finding or contributing some mechanism to get sort of the
same effect as a cross between:
*
weston_output_capture's support for using the DRM_MODE_CONNECTOR_WRITEBACK
connectors, and
*
the streamed orientation of weston_screen_recorder, and
*
no forced reliance on
Hi,
In the past there has been writing about Wayland's model using implicit
synchronization of GPU renderbuffers and KMS commits [1] [2].
It would sometimes be nice to do that waiting explicitly in a compositor before
enqueueing a KMS pageflip that references a buffer who may go on rendering fo
I have a DRM master implementing a purpose-built compositor for a dedicated
use-case. It drives several different connectors, each on its own vsync cadence
(there's no clone mode happening here).
The goal is to have commits to each connector occur completely without respect
to whatever is happe
Oh, facepalm. I didn’t even think to look at the numeric value. Sorry for the
confusion.
From: Simon Ser
Sent: Saturday, August 6, 2022 3:10:53 PM
To: Hoosier, Matt
Cc: Pekka Paalanen; dri-de...@lists.freedesktop.org;
wayland-devel@lists.freedesktop.org
Subject
From: Pekka Paalanen
Sent: Saturday, August 6, 2022 6:47:00 AM
To: Hoosier, Matt
Cc: wayland-devel@lists.freedesktop.org; dri-de...@lists.freedesktop.org
Subject: Re: How to test whether a buffer is in linear format
On Fri, 5 Aug 2022 12:32:01 +
"Hoosier,
Suppose that I want to map a GPU buffer to the CPU and do image analysis on it.
I know all the usual cautions about this being a poor performance option, etc.
But suppose for the moment that the use-case requires it.
What's the right set of preconditions to conclude that the buffer is in vanilla
On Thu, 2022-03-24 at 15:28 -0400, Alex Deucher wrote:
CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments unless
you trust the sender and know the content is safe.
On Thu, Mar 24, 2022 at 9:43 AM Hoosier, Matt <
<mailto:matt.hoos...@garmin.com>
matt.hoos...@g
On Thu, 2022-03-24 at 11:56 +0200, Pekka Paalanen wrote:
On Wed, 23 Mar 2022 14:19:08 +
"Hoosier, Matt" <
<mailto:matt.hoos...@garmin.com>
matt.hoos...@garmin.com
> wrote:
Hi,
I recently had a reason to wade through Mutter's code to support
systems with mor
Hi,
I recently had a reason to wade through Mutter's code to support systems with
more than one GPU. I was a bit surprised to see that it supports several
different strategies for dealing with scanning out a buffer on a KMS output not
associated with the GPU where the buffer was originally rend
ed in this way, with GDM running the DRM compositor and Mutter doing all
its work using Wayland-on-Wayland. That seems to have fizzled out. Does anybody
know why? Am I overlooking some obvious show-stopper here?
From: Guillermo Rodriguez
Date: Friday, October 22, 2021 at 7:04 AM
To make this a little more concrete, I put together MR
https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/702.
From: Hoosier, Matt
Sent: Friday, October 1, 2021 2:32:04 PM
To: wayland-devel@lists.freedesktop.org
Subject: Add z-order control into kiosk
I've been very happy to see kiosk-shell get introduced in the past year or so.
It seems to tick nearly every box that I frequently find myself wanting when
trying to do embedded deployment of pre-existing Wayland apps which expect to
use the customary desktop-centric shells:
* declarative
I put together
https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/180 .
From: Simon Ser
Sent: Wednesday, September 29, 2021 8:28:08 AM
To: Hoosier, Matt
Cc: Pekka Paalanen; wayland-devel@lists.freedesktop.org; Carsten Haitzler
Subject: Re: Any
nc() clues that already
existed.
Would anybody be interested in some kind of comment inserted into the
documentation for wl_buffer that expresses this implicit expectation?
-Matt
On 9/29/21, 4:38 AM, "Pekka Paalanen" wrote:
On Tue, 28 Sep 2021 13:16:36 +
"
Hi there,
Is there any definitive word about whether or not clients should be expected or
allowed to premultiply alpha the alpha channels in the normal EGL and
linux-dmabuf buffers they send to a compositor?
I have never seen this practice used with Wayland -- the shaders in the
gl-renderer
ame as a distinguishing/durable identifier of cards, and that the physical
path is the standard thing used to disambiguate. Thanks.
-Matt
On 9/23/21, 8:39 AM, "Pekka Paalanen" wrote:
On Wed, 22 Sep 2021 16:16:48 +0000
"Hoosier, Matt" wrote:
>
> The /dev/dri/by-
I get the intuition behind the suggestion to aggregate using logind seats, as
far as it goes. But it still seems to me that this just pushes the question
back: how do you identify which card is which in order to assign it to a seat?
Normally this is done using udev rules, right? Additionally, I'
I'm trying to find a robust way to handle the phrasing of UDev rules and
systemd dependencies about /dev/dri/cardXXX nodes to ensure that several
compositor services running on different graphics cards of a device all can
reliably start up.
First, some basic observations:
* The DRM su
> -Original Message-
> From: Derek Foreman
> Sent: Wednesday, August 25, 2021 3:54 PM
> To: Hoosier, Matt ; wayland-
> de...@lists.freedesktop.org
> Subject: Re: Discrepancies in object IDs printed by $WAYLAND_DEBUG
> output
>
> CAUTION - EXTERNAL EMAIL: Do
I observe that the IDs used to denote some wl_buffer protocol objects created
by a server-side factory in the $WAYLAND_DEBUG trace, differ between the moment
they're first announced in the callback event and the later use-sites when the
objects are passed to subsequent Wayland protocol method in
Thanks.
On 8/25/21, 11:16 AM, "Simon Ser" wrote:
CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments
unless you trust the sender and know the content is safe.
Yeah, you should be able to just destroy it right after create or
create_immed.
__
It's not totally clear from the documentation on linux-dmabuf-unstable-v1.xml
whether there's any need to keep the buffer-params object alive past the time
that create_immed() is used. The example programs in the Weston repository
don't bother to deallocate it at all in this case, but there does
39 matches
Mail list logo
