From a784b47533e6d43f74fcaa86e82843c5c9e308b8 Mon Sep 17 00:00:00 2001 From: Ankit Nautiyal Date: Mon, 22 Jul 2019 11:58:50 +0530 Subject: [PATCH] man: Update weston.ini, that no backend supports HDCP as yet Currently, the HDCP support in drm-backend is under review and no other backend supports HDCP yet. This patch is just to update the weston.ini with this information. Signed-off-by: Ankit Nautiyal --- man/weston.ini.man | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/man/weston.ini.man b/man/weston.ini.man index 7573573e..d19e461f 100644 --- a/man/weston.ini.man +++ b/man/weston.ini.man @@ -548,11 +548,12 @@ present. This seat can be constrained like any other. .TP 7 .BI "allow_hdcp=" true Allows HDCP support for this output. If set to true, HDCP can be tried for the -content-protection, provided by the backends, on this output. -The content-protection can actually be realized, only if the hardwares (source -and sink) support HDCP, and the backend has the implementation of -content-protection protocol. By default, HDCP support is always allowed for an -output. +content-protection, provided by the backends, on this output. By +default, HDCP support is always allowed for an output. The +content-protection can actually be realized, only if the hardware +(source and sink) support HDCP, and the backend has the implementation +of content-protection protocol. Currently, no backend actually +implements HDCP yet. .RE .SH "INPUT-METHOD SECTION" .TP 7