Re: [ANNOUNCE]: VM86 Daemon

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

This is interesting, but brings back a point I had in mind
for some time (regardless of having that daemon or not), which
is to provide a consistent API for fbdev's to provide EDID
informations to a "monitor" layer (or to userland) and for
fbdev's to setup appropriately based on EDID informations.

There are several issues here. One is the actual retreival of
the EDID data. There are several ways to do it, and all of them
must be implemented in an ideal world:

 - BIOS stuff (via something like your daemon)
 - Direct i2c (for all platforms that don't have a BIOS or cannot
   run it)
 - Other arch specific way (this includes what we do on some PPCs
   which is to retreive the EDID block from the device tree provided
   by the firmware).

Once the fbdev can provide, upon request, the EDID and probing info
(some cards can tell you if something is connected even without
providing an EDID, like on the S-Video output, or on the VGA output
with a non-DDC capable monitor), we need some consistent API to
retreive that from, userland at least

Then, we need fbdev to "validate" modes based on those EDID infos
(via fbmon ?).




-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/