View Single Post
Old 01-05-07, 12:03 AM   #3
sandeen
Registered User
 
Join Date: Dec 2006
Posts: 6
Default Re: Wrongly rejected interlaced modes from EDID?

Maybe I'm confused about how interlacing affects vert refresh... but here's another oddity. I put the EDID-interpreted timings in as a modeline, and the driver seems to treat it differently even though they are the same values....

Modeline:

Code:
 Modeline "1920x1080" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync Interlace
Code:
(II) NVIDIA(0):   Validating Mode "1920x1080":
(II) NVIDIA(0):     1920 x 540 @ 60 Hz
(II) NVIDIA(0):     Mode Source: X Configuration file ModeLine
(II) NVIDIA(0):       Pixel Clock      : 74.25 MHz
(II) NVIDIA(0):       HRes, HSyncStart : 1920, 2008
(II) NVIDIA(0):       HSyncEnd, HTotal : 2052, 2200
(II) NVIDIA(0):       VRes, VSyncStart :  540,  542
(II) NVIDIA(0):       VSyncEnd, VTotal :  547,  562
(II) NVIDIA(0):       H/V Polarity     : +/+
(II) NVIDIA(0):       Extra            : Interlace
(WW) NVIDIA(0):     Mode is rejected: HorizSync (33.8 kHz) out of range
(WW) NVIDIA(0):     (28.000-33.000 kHz).
EDID:
Code:
(II) NVIDIA(0):   Validating Mode "1920x1080":
(II) NVIDIA(0):     1920 x 540 @ 60 Hz
(II) NVIDIA(0):     Mode Source: EDID
(II) NVIDIA(0):       Pixel Clock      : 74.25 MHz
(II) NVIDIA(0):       HRes, HSyncStart : 1920, 2008
(II) NVIDIA(0):       HSyncEnd, HTotal : 2052, 2200
(II) NVIDIA(0):       VRes, VSyncStart :  540,  542
(II) NVIDIA(0):       VSyncEnd, VTotal :  547,  562
(II) NVIDIA(0):       H/V Polarity     : +/+
(II) NVIDIA(0):       Extra            : Interlace
(WW) NVIDIA(0):     Mode is rejected: VertRefresh (120.1 Hz) out of range
(WW) NVIDIA(0):     (59.000-61.000 Hz).
at least the parsing/verification is going differently, because it chokes for different reasons despite the same values... what's up with this?
sandeen is offline   Reply With Quote