Hi Scott,
As this was under discussion in last patchset, summarizing it here again:
HDCP2.2 spec leaves the content-type classification to the
content-provider (client).
The same had been discussed earlier in #wayland, and the mailing list:
https://lists.freedesktop.org/archives/wayland-deve
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
On 11/22/2018 1:01 PM, C, Ramalingam wrote:
Hi Scott,
I am working on enabling the HDCP1.4 and 2.2 in kernel and Weston from
Intel. Would like to share some points here.
On 11/21/2018 7:35 AM, Scott Anderson wrote:
Hi,
As far as I understand, the different types and versions of
protectio
Hi Scott,
I am working on enabling the HDCP1.4 and 2.2 in kernel and Weston from
Intel. Would like to share some points here.
On 11/21/2018 7:35 AM, Scott Anderson wrote:
Hi,
As far as I understand, the different types and versions of protection
a client would want is based on the resolutio
Hi,
As far as I understand, the different types and versions of protection a
client would want is based on the resolution of the content, rather than
anything about what the content actually is. Is there any particular
reason a client would care if their content is being used on a higher
HDCP
On 11/19/2018 12:51 PM, Simon Ser wrote:
On Monday, November 19, 2018 4:21 AM, wrote:
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
On Monday, November 19, 2018 4:21 AM, wrote:
> 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 cl
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
