[PATCH] xrandr: document how to disconnect RandR 1.4 providers

Aaron Plattner aplattner at nvidia.com
Fri Mar 21 10:38:59 PDT 2014


Commit a6217be2d5a93a4c7b48f4081a4a8e14c3c97014 restored the ability to
disconnect RandR 1.4 providers from each other, but it's not clear from the
documentation how to actually do that.  Try to clarify by mentioning it in the
man page.

Cc: Dave Airlie <airlied at gmail.com>
Signed-off-by: Aaron Plattner <aplattner at nvidia.com>
---
I plan to make a new release after this change.  Dave, did I get the order right
on the --setprovideroutputsink wording?

 man/xrandr.man | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/man/xrandr.man b/man/xrandr.man
index 93c37aa80858..73d337c9eaa0 100644
--- a/man/xrandr.man
+++ b/man/xrandr.man
@@ -126,10 +126,14 @@ Report information about the providers available.
 Set \fIsource\fP as the source of display output images for \fIprovider\fP.
 This is only possible if \fIsource\fP and \fIprovider\fP have the \fBSource
 Output\fR and \fBSink Output\fR capabilities, respectively.
+If \fIsource\fP is \fB0x0\fP, then \fIprovider\fP is disconnected from its
+current output source.
 .IP "\-\-setprovideroffloadsink \fIprovider\fP \fIsink\fP"
 Set \fIprovider\fP as a render offload device for \fIsink\fP.
 This is only possible if \fIprovider\fP and \fIsink\fP have the \fBSource
 Offload\fR and \fBSink Offload\fR capabilities, respectively.
+If \fIsink\fP is \fB0x0\fP, then \fIprovider\fP is disconnected from its current
+render offload sink.
 .PP
 .SH "RandR version 1.3 options"
 .PP
-- 
1.9.0



More information about the xorg-devel mailing list