OpenSolaris

Printable Version Enter a New Search
Bug ID 6531742
Synopsis Radeon driver's own mode validation code does not work properly
State 10-Fix Delivered (Fix available in build)
Category:Subcategory xserver:devices_x86
Keywords s10patch-approved
Responsible Engineer Henry Zhao
Reported Against
Duplicate Of
Introduced In
Commit to Fix snv_61
Fixed In snv_61
Release Fixed solaris_nevada(snv_61) , solaris_10u4(s10u4_08) (Bug ID:2149075)
Related Bugs 6494769
Submit Date 6-March-2007
Last Update Date 8-May-2007
Description
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 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. This is the cause to 

    6494769 Xorg doesn't work in Remote Control for IBM BladeCenter servers that 
    use the ATI ES1000 

    where a VESA mode with different polarity is picked instead of EDID mode in
    detailed timing sector.

(2) 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.
Work Around
N/A
Comments
N/A