All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul A. Clarke" <pc@us.ibm.com>
To: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org,
	Petr Vandrovec <petr@vandrovec.name>
Subject: Re: [PATCH] matroxfb: another attempt to rectify jitter (G450/G550)
Date: Thu, 15 Feb 2007 14:47:27 -0600	[thread overview]
Message-ID: <45D4C6DF.5050002@us.ibm.com> (raw)
In-Reply-To: <20070131222500.GA16283@sci.fi>

Ville,

Ville Syrjälä wrote:
> I see. It seems to always use VIDPLL with CRTC2. So if DVICLK is to be 
> used with CRTC2 it apparently needs to be added in the VIDPLL case. 
> Hmmm. I wonder if the code even supports CRTC2+DVI because the CRTC2 
> code seems to leave the C2PIXCLK selection to PCICLK if CRTC2 drives DVI 
> only. Did you try to map CRTC2 to DVI?

So, I just (finally) ran the following tests, on a SLES10 system (2.6.16+) with 
G450, both with and without the patch (results were identical):

- with "video=matroxfb:outputs:012"
                   D-shell               DVI-D
on boot             OK                   junk
X dual fb0/fb1      OK                    OK
X fb0 only         black(!)              junk
X fb1 only        signal problems(!)     OK, but yellow(?)

- with "video=matroxfb:outputs:021"
                   D-shell               DVI-D
on boot            junk                   OK
X dual fb0/fb1      OK                    OK
X fb0 only         junk                   OK
X fb1 only        OK, but yellow        OK (blank)

Note that I ignored the DVI-A output, which is apparently the first "output". 
Earlier testing showed pretty much what I'd expect on that channel.

So, it appears that CRTC2 can indeed drive DVI-D.

It also appears that this area still needs work, but any objections to moving 
the suggested patch into -mm ?  It provides clean signals and removes the 
platform-specific hacked ifdefs.

-- 
Regards,
Paul Clarke

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-02-15 20:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23  0:17 [PATCH] matroxfb: another attempt to rectify jitter (G450/G550) Paul A. Clarke
     [not found] ` <45BC58E9.9020306@vandrovec.name>
2007-01-30 20:22   ` Paul A. Clarke
2007-01-31 11:54     ` Ville Syrjälä
2007-01-31 21:58       ` Paul A. Clarke
2007-01-31 22:25         ` Ville Syrjälä
2007-02-15 20:47           ` Paul A. Clarke [this message]
2007-02-16 17:29             ` Ville Syrjälä
2007-02-17  6:34               ` Petr Vandrovec

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=45D4C6DF.5050002@us.ibm.com \
    --to=pc@us.ibm.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=petr@vandrovec.name \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.