summaryrefslogtreecommitdiff
path: root/randrproto.txt
diff options
context:
space:
mode:
authorAdam Jackson <ajax@redhat.com>2011-05-19 16:26:27 -0400
committerAdam Jackson <ajax@redhat.com>2011-05-19 16:26:27 -0400
commitb5c977ad70b845c278ef52c004d9e5fc3ec97cbf (patch)
treeca07a5eff52a8584249b8187aa2da9d351c7381e /randrproto.txt
parent105a161a3f5fb67f5fe7e4119629d424672804aa (diff)
Remove nonsense paragraph about dual-link DVI
I've never heard of any hardware that behaves so. Signed-off-by: Adam Jackson <ajax@redhat.com>
Diffstat (limited to 'randrproto.txt')
-rw-r--r--randrproto.txt5
1 files changed, 0 insertions, 5 deletions
diff --git a/randrproto.txt b/randrproto.txt
index 20cac75..ce462ea 100644
--- a/randrproto.txt
+++ b/randrproto.txt
@@ -105,11 +105,6 @@ the hardware will probably impose restrictions on the possible
configurations. The protocol doesn't try to describe these restrictions,
instead it provides a mechanism to find out what combinations are supported.
-For instance, dual-link DVI gangs two CRTC outputs together to provide higher
-bandwidth for large resolution screens. This is exposed in RandR by
-requiring that nothing be connected to the second CRTC when driving a high
-resolution screen on the first.
-
1.3 Introduction to version 1.3 of the extension
Version 1.3 builds on the changes made with version 1.2 and adds some new