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 <ankit.k.nautiyal@intel.com>
This commit is contained in:
parent
04f7646dee
commit
a784b47533
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user