Bug 33127
Summary: | QA0322 - RFE: DCC returned data not being well used? | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | R P Herrold <herrold> |
Component: | Xconfigurator | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-25 19:59:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
R P Herrold
2001-03-25 19:59:37 UTC
Recent versions of Xconfigurator do make efficient use of DDC. they get the EDID, look up the monitor in the database, and use that timing info if present. If not present, it falls back to the DDC timing info, if that appears sane. If it appears insane (and yes, some monitors have an EDID but report refresh rates that are totally out of whack), it then makes you choose. The monitor EDID data sharing with Red Hat is a good idea, we'll have to figure out how to best implement getting such data back to us. |