From: Scott Anderson
This protocol allows a client to ask the compositor to only allow it to
be displayed on a "secure" output (e.g. HDCP).
This is based on a chromium protocol of the same name [1].
This protocol is mostly useful for closed systems, where the client can
trust the compositor, su
Le 28/11/2018 à 02:15, Peter Hutterer a écrit :
> On Tue, Nov 27, 2018 at 11:25:05AM +0100, Colomban Wendling wrote:
>> […]
>> * Use the "flat" acceleration profile for slow mode
>> - This works fairly well and allows for very low pointer speeds.
>> - The main question is: is there a sensible w
Hi Pekka,
> I suppose the compositor-side copy of buffers you mentioned is for the
> lack of release fences, not acquire fences?
Yes, the lack of release fences is the very reason for the copy. I could
cook something up for the acquire fence, but that wouldn't synchronise the
buffer access anyway.
On Tue, 27 Nov 2018 18:25:04 +0200
Alexandros Frantzis wrote:
> On Tue, Nov 27, 2018 at 05:17:40PM +0200, Alexandros Frantzis wrote:
> > On Tue, Nov 27, 2018 at 10:53:45AM +0200, Pekka Paalanen wrote:
> > > Yes, we probably should have some wording that if a client is letting
> > > something li
On Tue, 27 Nov 2018 14:57:07 +
Tomek Bury wrote:
> Hi Pekka,
>
> I'm just trying to figure out how to use this extension in a driver.
> Without this extension the only option I have is to take a copy if each
> wl_buffer on the compositor-side. I can't really do implicit sync so I'm
> really
On Wed, 28 Nov 2018 09:49:54 +0900
박성진 wrote:
> > On Tue, 27 Nov 2018 17:59:16 +0900
> > 박성진 wrote:
>
> > > Hi Derek>> On 11/22/18 11:08 PM, Jeonghyun Kang wrote:
>
> > > > What if it's a frame event that gets dropped and not an input event? Or
> > > > a resource destroy?
> > > Instead of des
