[Bug 10205] New: Radeon driver's own mode validation code does not work properly

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 6 17:29:24 PST 2007


           Summary: Radeon driver's own mode validation code does not work
           Product: xorg
           Version: 7.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: henry.zhao at sun.com
         QAContact: xorg-team at lists.x.org

Radeon driver uses its own mode validation code when the monitor is LCD/DFP. 
The code assumes the existance of EDID modes, and adds modes in all sectors 
(detailed, established and standard) to the mode database and sort them. For 
modes without timing data (established and standard), it picks a mode of the 
same size with highest clock rate from default VESA modeline database. The 
code used in this process has two problems:

(1) It does not process user defined modelines (with config file) properly.

(2) It does not give priority to EDID mode from detailed timing sector. If
    a mode exits both in EDID and VESA database, it picks one with higher
    clock rate. 

(3) VESA modeline database is organized such that double scan lines are 
    inserted every another line. In VESA modeline database search, the code 
    uses p->next->next to skip double scan line, which does not work 
    correctly when user defined modes are added to the database.

Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the xorg-driver-ati mailing list