linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Selli <dhatarattha@route-add.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Jitter on Matrox G450 in Xorg
Date: Sat, 30 Aug 2008 19:39:47 +0200	[thread overview]
Message-ID: <48B985E3.4060901@route-add.net> (raw)

   Hello,
	I am experiencing a jitter under Xorg 7.2 with a G450 AGP card on a 
VIA, AMD K6-II PC.  I noticed this happens with kernels 2.6.23 and later.

   Investigating this, I read on 
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.23:

commit e798bd95b61918e653f3d28f9176237236f2d103
Author: Paul A. Clarke <pc@us.ibm.com>
Date:   Fri Aug 10 13:00:49 2007 -0700

     matroxfb: rectify jitter (G450/G550)

     This builds upon my previous attempts to resolve some jitter
     problems seen with the Matrox G450 and G550 -based cards,
     including odd disparities observed between x86 and Power -based
     machines in a somewhat less hackish way (removing the hacked
     ifdefs).

     Apparently, preference should be given to use the DVI PLL when
     frequencies permit, the Standard PLL otherwise.  The max pixel clock
     for the panellink interface is extracted from the PInS information
     on the card and used as a limit to determine which PLL to use.


   The same information, with diffs, I could read on the following post 
from this ML's archive: 
http://sourceforge.net/mailarchive/message.php?msg_id=46B0396C.1020407%40gmail.com

   I am not 100% sure this has to do with the framebuffer driver or with 
some other kernel driver that xorg uses (DRM_MGA?), but so far I only 
found jitter issues concerning the matroxfb driver and did not find 
references to the mga driver in the above changelog.

   If the jitter I am experiencing is due to the above change, I wonder 
if there is a way to revert to the old mechanism without modifying the 
driver source code and recompiling.  That is, I wonder if there is a 
driver load-time parameter that allows trying first the DVI PLL when 
possible, or sticking to the Standard PLL regardless.

   BTW, how can I see which PLL the driver is currently using?


   Thank you,

-- 
Alessandro Selli
Tel: 340.839.73.05
http://alessandro.route-add.net
Chiave PGP/GPG key: EC885A8B

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

                 reply	other threads:[~2008-08-30 17:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48B985E3.4060901@route-add.net \
    --to=dhatarattha@route-add.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).