Bug 169504 - ddcprobe doesn't give detected manufacturer's timing modes
ddcprobe doesn't give detected manufacturer's timing modes
Product: Fedora
Classification: Fedora
Component: kudzu (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-09-28 22:39 EDT by Philip Prindeville
Modified: 2014-03-16 22:56 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-03 14:59:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Philip Prindeville 2005-09-28 22:39:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc3 Firefox/1.0.6

Description of problem:
The output of "ddcprobe --monitor" doesn't give timing modes, such as resolutions that the monitor can display that aren't standardized (e.g. VESA).

Other information such as sync and R, G, B, colorspace and Gamma values etc. would also be extremely handy when trying to autogenerate configurations (i.e. xorg.conf, etc).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run "ddcprobe --monitor"
2. look for timing, gamma values, resolution modes, etc.

Actual Results:  Don't get the timing, gamma value, resolutions, etc.

Expected Results:  The missing information should be given.

Additional info:
Comment 1 Bill Nottingham 2005-10-03 14:59:13 EDT
This probably won't be added at any point in the near future. Especially since
the DDC code is so limite architecturally, it's best to get the recognition done
in the driver itself.

Note You need to log in before you can comment on or make changes to this bug.