Bug 169504

Summary:	ddcprobe doesn't give detected manufacturer's timing modes
Product:	[Fedora] Fedora	Reporter:	Philip Prindeville <philipp>
Component:	kudzu	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WONTFIX	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	rvokal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-03 18:59:13 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 Philip Prindeville 2005-09-29 02:39:10 UTC

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):
rhpl-0.148.1-2

How reproducible:
Always

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

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 18:59:13 UTC

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.