From: Keith Packard Subject: Re: Difference in dot clock between xserver 1.5.2 and 1.9.4 - intel driver Date: Mon, 28 Feb 2011 07:29:23 -0800 Message-ID: References: <431561.15280.qm@web110507.mail.gq1.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0409599644==" Return-path: Received: from keithp.com (home.keithp.com [63.227.221.253]) by gabe.freedesktop.org (Postfix) with ESMTP id 72E249EEF6 for ; Mon, 28 Feb 2011 07:29:27 -0800 (PST) In-Reply-To: <431561.15280.qm@web110507.mail.gq1.yahoo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: SD , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============0409599644== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable On Mon, 28 Feb 2011 03:54:24 -0800 (PST), SD wrote: > (II) intel(0): using SSC reference clock of 96 MHz That's the spread-spectrum clock reference value; it forms the basis From=20which the actual dot clock is computed using a PLL. It is *not* the actual dot clock. > [ 135.556] (II) intel(0): clock: 65.0 MHz Image Size: 304 x 228 > mm And there's the actual dot clock. > And in MHz can be only dot clock, but if I use 1024x768x60Hz =3D ~ 47.2 M= Hz and we need to multiply on 3 (subpixels), it will be ~140 MHz > I know that 96 in xserver 1.5.2 is not 140 but it is much closer to > it, then 65. You don't multiply by three; each channel has it's own wire in LVDS. But, you have to add space for the retrace intervals. The standard VESA mode for 1024x768x60 uses a 65MHz dot clock. > Why in xserver 1.5.2 intel driver shows 96 MHz but in 1.9.4 it does > only 65 MHz. And can it be the reason why my LCD shows picture like it > use less then 50Hz vsync. I'll bet both are using the same timings, but you can check for yourself with the 'xrandr' utility: $ xrandr --verbose ... 1440x900 (0x45) 74.1MHz -HSync -VSync *current +preferred h: width 1440 start 1464 end 1480 total 1600 skew 0 clock 46.= 3KHz v: height 900 start 903 end 909 total 926 clock 50.= 0Hz ... The mode marked '*current' is what the system is currently using. You can help figure out what the problem is by running the 'intel_reg_dumper' utility on both distributions. That's available from: git://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools Doing a 'diff' on the output of this under the two operating systems will show every change in programming for your machine. =2D-=20 keith.packard@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFNa79TQp8BWwlsTdMRAv61AKCbFckG9G17pY1wChXeVXjlDEnAuACdELRU KlmIKwiFKqJPTYFaLYRACJA= =ymmH -----END PGP SIGNATURE----- --=-=-=-- --===============0409599644== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0409599644==--