> From: Brian Starkey
> Sent: Tuesday, June 18, 2024 4:11 AM
> To: Dmitry Baryshkov
> Cc: Hoosier, Matt ; Daniel Vetter ;
> dri-devel@lists.freedesktop.org; Pekka Paalanen
> ; n...@arm.com
> Subject: Re: Correct sequencing of usage of DRM writeback connector
>
> Hi
>> >> >> There is a discussion ongoing over in the compositor world about the
>> >> >> implication
>> Hi,
>>
>> On Mon, Jun 17, 2024 at 05:16:36PM +0200, Daniel Vetter wrote:
>> >On Mon, Jun 17, 2024 at 01:41:59PM +, Hoosier,
Hi,
There is a discussion ongoing over in the compositor world about the
implication of this cautionary wording found in the documentation for the
DRM_MODE_CONNECTOR_WRITEBACK connectors:
> * "WRITEBACK_OUT_FENCE_PTR":
> *Userspace can use this property to provide a pointer for the kerne
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-devel@lists.freedesktop.org;
wayland-de...@lists.freedesktop.org
Subject
From: Pekka Paalanen
Sent: Saturday, August 6, 2022 6:47:00 AM
To: Hoosier, Matt
Cc: wayland-de...@lists.freedesktop.org; dri-devel@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
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
11 matches
Mail list logo
