On 2/1/2019 6:15 PM, Pekka Paalanen wrote:
On Mon, 28 Jan 2019 22:39:39 +0530
"Nautiyal, Ankit K" wrote:
Hi Simon Ser,
Thanks for your comments.
I am also not sure about whether the protocol belongs here or not, and
that's why I had first proposed the same in weston, along with the
implementat
On Mon, 28 Jan 2019 22:39:39 +0530
"Nautiyal, Ankit K" wrote:
> Hi Simon Ser,
> Thanks for your comments.
> I am also not sure about whether the protocol belongs here or not, and
> that's why I had first proposed the same in weston, along with the
> implementation and the client application -
>
Hi Simon Ser,
Thanks for your comments.
I am also not sure about whether the protocol belongs here or not, and
that's why I had first proposed the same in weston, along with the
implementation and the client application -
Merge request:
_https://gitlab.freedesktop.org/wayland/weston/merge_reque
Hi,
Thanks for your patch. However, I don't think it belongs to wayland-protocols.
wayland-protocols isn't designed for all common Wayland protocols. For instance,
the IVI shell isn't there, and has a similar use-case (although not limited to
closed systems). Also some other protocols like layer-s
From: Ankit Nautiyal
This patch adds the protocol for providing content-protection to a
client application. The content-protection here refers to the 'on the
wire protection' e.g. HDCP1.4 HDCP2.2.
The client application can request for the content-protection,
specifying the type of the content: T
