[Bug 87508] New: Max pixel clock in EDID should be overridden by highest clock in mode descriptor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 19 12:05:08 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=87508

            Bug ID: 87508
           Summary: Max pixel clock in EDID should be overridden by
                    highest clock in mode descriptor
           Product: xorg
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/intel
          Assignee: chris at chris-wilson.co.uk
          Reporter: adamvleggett at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org

I have a Sony XBR 4K TV connected to the Haswell Refresh graphics on my
i7-4790K. The following appears in the xorg log:

[ 9.308] (II) intel(0): Not using mode "4096x2160" (bad mode
clock/interlace/doublescan)
[ 9.308] (II) intel(0): Not using mode "4096x2160" (bad mode
clock/interlace/doublescan)
[ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode
clock/interlace/doublescan)
[ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode
clock/interlace/doublescan)
[ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode
clock/interlace/doublescan)
[ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode
clock/interlace/doublescan)
[ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode
clock/interlace/doublescan)

This seems to appear for no better reason than because the EDID claims a max
pixel clock of 165.0MHz.

If the EDID contains modes that exceed the EDID's own claimed max pixel clock,
the max pixel clock should be adjusted. This appears to be what the nVidia
proprietary driver does.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141219/004335eb/attachment.html>


More information about the intel-gfx-bugs mailing list