<font face="courier new,monospace"><br></font><br><div class="gmail_quote">On Wed, Oct 27, 2010 at 11:15 AM, Pasi Kärkkäinen <span dir="ltr"><<a href="mailto:pasik@iki.fi" target="_blank">pasik@iki.fi</a>></span> wrote:<br>
<br>... snip ...<br>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I was asking about the "monitor connected but turned off" thing<br>
on dri-devel, and the reply was that it's impossible to detect<br>
if the display is turned on or off. Displays are designed<br>
to always send the EDID info, no difference if they're on or off.<br>
<br>
So.. we can't detect that. And others can't either.<br></blockquote><div><br>I had discovered this too, because, I wanted to be able to report on<br>my management system when monitors attached to remote display<br>
systems had been accidentally turned off, or partly died. Sadly I can't.<br><br>But I can get all sorts of manufacturer info and physical/resolution info<br>(for asset management purposes).<br><br>So I'm going to hijack this thread a little and ask if anyone can<br>
point me to a resource that can tell me (at the lowest level) what<br>I need to interact with (what hardware bus I need to send messages on)<br>to send the request for EDID info to a monitor and get the results<br>so I can decode them. (I have the message format info, I just don't<br>
know where to send/receive the stuff.<br><br>Can anyone enlighten me?<br><br>TIA<br>Fulko<br><br></div></div>