Bug 75086 (freqsigfigs)

Summary: an-additional-decimal-for-frequencies-refresh-rates
Product: xorg Reporter: Kevin Mitchell <kevmitch>
Component: App/xrandrAssignee: Keith Packard <keithp>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: aplattner
Version: git   
Hardware: Other   
OS: Linux (All)   
URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736224
Whiteboard:
i915 platform: i915 features:

Description Kevin Mitchell 2014-02-17 10:49:34 UTC 
I have an Samsung eh5000 HDTV that I connect to my Intel Mobile Ivy
Bridge chipset via HDMI1 as reported by xrandr. Without modification
xrandr reports the display's native resolution as

1920x1080      60.0 +   59.9     30.0     24.0     30.0     24.0*

This is confusing because it lists 30.0 and 24.0 twice each. I
discovered that I could switch to either one by specifying --rate
30/--rate 29.97 or --rate 24/--rate 23.98.
Comment 2 Aaron Plattner 2014-03-21 17:41:16 UTC 
I pushed an earlier change from Ville Syrjälä for this.

commit 8f9b993342fddfceaa1afbec2996ce10038f10d7
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri May 31 17:01:53 2013 +0300

    xrandr: Use more decimal places when printing various rates
    
    Using just one decimal place for dotclock and refresh rates loses quite
    a bit of information. When dealing with 60Hz vs. 59.94Hz refresh rate
    modes for example, it's useful to see at least two decimal places. For
    the dotclock in similar cases, three decimal places seems quite a bit
    better than just one.
    
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Reviewed-by: Aaron Plattner <aplattner@nvidia.com>

 xrandr.c | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

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.