[prev in list] [next in list] [prev in thread] [next in thread]
List: wine-devel
Subject: Re: winex11.drv: xrandr1.2 don't assume CRTC 0 is active
From: siro () das-labor ! org
Date: 2012-07-30 20:05:11
Message-ID: E1SvwEC-0002bd-2a () wine ! codeweavers ! com
[Download RAW message or body]
[Attachment #2 (text/html)]
<html><head></head><body>As far as I understood CRTC 0 is disabled, because it is \
only capable of generating analog video signals. I'm using a HDMI monitor, which is \
controlled by CRTC 1. To use multihead (not clone), you have to connect a analog \
(VGA) and digital monitor (in my case). Each monitor will use one CRTC and each CRTC \
will show a different part of the same screen. With this in mind every active CRTC \
should be listed as "native Windows \
monitor".<div>Regards,</div><div>Patrick</div><div><hr><div><strong>Von:</strong> \
"Henri Verbeet" <hverbeet@gmail.com><br><strong>An:</strong> "Alexandre \
Julliard" <julliard@winehq.org><br><strong>Cc:</strong> "Patrick Rudolph" \
<siro@das-labor.org>, "wine-devel@winehq.org" \
<wine-devel@winehq.org><br><strong>Gesendet:</strong> 30. Juli 2012 \
21:47<br><strong>Betreff:</strong> Re: winex11.drv: xrandr1.2 don't assume CRTC 0 is \
active<br></div><br><pre>On 30 July 2012 20:13, Alexandre Julliard \
<julliard@winehq.org> wrote:
> This clearly needs a helper function.
>
I'm not sure if this really makes sense to begin with. CRTC 0 is
supposed to be the primary display. With proper multihead support we'd
be able to enumerate the other display as well, and change modes on
them etc., but I suspect disabling the primary display isn't going to
give very good results on native Windows either, except perhaps for
applications that have multihead support themselves.
</julliard@winehq.org></pre></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic