On Wed, Oct 27, 2010 at 11:15 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
... snip ...
I had discovered this too, because, I wanted to be able to report on
my management system when monitors attached to remote display
systems had been accidentally turned off, or partly died. Sadly I can't.
But I can get all sorts of manufacturer info and physical/resolution info
(for asset management purposes).
So I'm going to hijack this thread a little and ask if anyone can
point me to a resource that can tell me (at the lowest level) what
I need to interact with (what hardware bus I need to send messages on)
to send the request for EDID info to a monitor and get the results
so I can decode them. (I have the message format info, I just don't
know where to send/receive the stuff.
Can anyone enlighten me?
TIA
Fulko
... snip ...
I was asking about the "monitor connected but turned off" thing
on dri-devel, and the reply was that it's impossible to detect
if the display is turned on or off. Displays are designed
to always send the EDID info, no difference if they're on or off.
So.. we can't detect that. And others can't either.
I had discovered this too, because, I wanted to be able to report on
my management system when monitors attached to remote display
systems had been accidentally turned off, or partly died. Sadly I can't.
But I can get all sorts of manufacturer info and physical/resolution info
(for asset management purposes).
So I'm going to hijack this thread a little and ask if anyone can
point me to a resource that can tell me (at the lowest level) what
I need to interact with (what hardware bus I need to send messages on)
to send the request for EDID info to a monitor and get the results
so I can decode them. (I have the message format info, I just don't
know where to send/receive the stuff.
Can anyone enlighten me?
TIA
Fulko
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
