Summary: | Please put EDID data on root window | ||
---|---|---|---|
Product: | xorg | Reporter: | Ross Burton <ross> |
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | enhancement | ||
Priority: | high | CC: | daniel, ku.b, libv |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Ross Burton
2005-07-29 23:38:27 UTC
A couple of other approaches are to: a) pack the EDID data in a defined format so you can get per-screen EDID information to the property, b) ... I don't know what b was. I had this tab open before I went out to dinner and stuff, and now it's a lot later, and ... it's been a long Friday night, and I don't know. Probably something about a generic display properties API for stuff like EDID, colour management, whatever, as an extension. Or something. 3. put EDID in every root property first EDID is called "XFree86_DDC_EDID1_RAWDATA" as is now all following EDID blocks are called XFree86_DDC_EDID1_RAWDATA_[screen_number] -> XFree86_DDC_EDID1_RAWDATA_1 XFree86_DDC_EDID1_RAWDATA_2 ... Thus the overhead is minimal for existing applications is minimal. Ok there not that many. Profiles can be stored the same way by appending the screen number. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. For Oyranos requiring means for identificating the attached monitor, I specified the requirements as suggested in my previous comment here. See: http://www.oyranos.org/wiki/index.php?title=Oyranos_X11_Requirements#Multi_Monitor_EDID_in_X11 This is available as a RANDR property now. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.