<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - intel-virtual-output: Support for rotated displays"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71846">71846</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>chris@chris-wilson.co.uk
</td>
</tr>
<tr>
<th>Summary</th>
<td>intel-virtual-output: Support for rotated displays
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mail@kirill-mueller.de
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/intel
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr></table>
<p>
<div>
<pre>I am testing a tri-head setup on 13.10 with my Lenovo T430 with the new
xserver-xorg-video-intel. I have my laptop screen, DP1 right of it, and DP2
right of it -- rotated. This works with puetzk's screenclone, I also need to
specify rotation for the second screen of DISPLAY :8 and use a "rotated" mode
(1200x1920) for the second virtual screen. (See
<a href="http://askubuntu.com/a/303897/30266">http://askubuntu.com/a/303897/30266</a> for more information.)
I wonder if `intel-virtual-output` could be enhanced to support rotated
displays.
If possible, I would like to use `intel-virtual-output` instead of
`screenclone` because it does all necessary setup. I'll be glad to test a patch
before it's applied upstream.
Note that, with the default xserver-xorg-video-intel in Ubuntu 13.10, the
virtual screen cannot be rotated using `xrandr --rotate ...`. Using a "rotated"
mode (1200x1920) works.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>