View Single Post
Old 06-21-05, 03:05 AM   #34
nox771
Registered User
 
Join Date: Jun 2005
Posts: 2
Default Re: 7664 and 1600x1200 (maximum pixel clock?)

Quote:
Originally Posted by freelsjd
Modeline "1600x1200" 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
I got curious about this modeline and did some checking. Using this page:

http://www.tkk.fi/Misc/Electronics/f...2rgb/calc.html

it looks like that modeline is the VESA timing for 1600x1200. Further, looking at the monitor specs on the Samsung 213T and the Dell, they both support 162MHz clocks (which matches the VESA timing):

http://www.samsung.com/au/products/m...Specifications
http://support.dell.com/support/edoc...lish/specs.htm

This all makes it look like the DVI connection should support at least 162MHz (and higher for larger panels). My log also shows the 135MHz limit. I don't know why it is there, it seems arbitrary, its not a monitor limitation. The modeline I pulled came from the 'nv' log, which had the following:
(II) NV(0): Supported VESA Video Modes:
(II) NV(0): 720x400@70Hz
(II) NV(0): 640x480@60Hz
(II) NV(0): 640x480@67Hz
(II) NV(0): 640x480@72Hz
(II) NV(0): 640x480@75Hz
(II) NV(0): 800x600@56Hz
(II) NV(0): 800x600@60Hz
(II) NV(0): 800x600@72Hz
(II) NV(0): 800x600@75Hz
(II) NV(0): 832x624@75Hz
(II) NV(0): 1024x768@60Hz
(II) NV(0): 1024x768@70Hz
(II) NV(0): 1024x768@75Hz
(II) NV(0): 1280x1024@75Hz
(II) NV(0): 1152x870@75Hz
(II) NV(0): Manufacturer's mask: 0
(II) NV(0): Supported Future Video Modes:
(II) NV(0): #0: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) NV(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) NV(0): Supported additional Video Mode:
(II) NV(0): clock: 130.4 MHz Image Size: 432 x 324 mm
(II) NV(0): h_active: 1600 h_sync: 1648 h_sync_end 1680 h_blank_end 1760 h_border: 0
(II) NV(0): v_active: 1200 v_sync: 1202 v_sync_end 1206 v_blanking: 1235 v_border: 0
(II) NV(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
I don't know where the "additional" mode comes from, but it seems to work on the Samsung (it is not VESA timing). It seems the real fix is to remove the 135MHz limit from the driver.
nox771 is offline   Reply With Quote