[haiku-development] Re: [RFC] Common accelerant connector language

  • From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sat, 14 May 2016 11:08:38 +0200

Am 13/05/2016 um 22:45 schrieb Alexander von Gluck IV:

May 13 2016 2:19 AM, "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote:
Am 12/05/2016 um 20:37 schrieb Alexander von Gluck IV:

monitor_info seems unused still by any accelerant.

IIRC, as long as the driver can provide EDID information, the app_server will 
translate that
automatically -- only if the driver cannot provide EDID, it'll need to fill out 
the monitor_info
itself.
It's been some time, though :-)
Ah.. so monitor_info was originally more of a fallback if EDID was unavailable?

No, it's what is used internally, as well as in the user API. EDID is a bit unhandy for that, and monitor_info is supposed to deliver all the needed information :-)
If a driver cannot deliver EDID, though, it may still be able to fill out the monitor_info data directly. Plus, since all drivers usually deal with EDID information, it seemed natural to put the conversion into the app_server instead of duplicating it in every add-on.

I guess we could repurpose monitor_info for "attachment information" like
positioning (left of center, right of center, etc) and port information 
(hdmi,dvi,etc)

It seems like a nice new "Haiku only (aka non-Be)" entry point for a pipeline 
of communication
between the accelerants and the BScreen.

Since EDID probably doesn't hold all necessary information, the app_server could then offer a utility function to convert EDID into a partial monitor_info.

Bye,
   Axel.


Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 05-2016