All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul A. Clarke" <pc@us.ibm.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-fbdev-devel@lists.sourceforge.net, Ian Romanick <idr@us.ibm.com>
Subject: Re: [Fwd: [PATCH][matroxfb] G450 jittery display on ppc systems]
Date: Wed, 12 Apr 2006 19:11:00 -0500	[thread overview]
Message-ID: <443D9714.3070300@us.ibm.com> (raw)
In-Reply-To: <443D70A7.8020702@vc.cvut.cz>

Petr Vandrovec wrote:
> Paul A. Clarke wrote:
>> Just a polite nudge on this patch
[...]
> It looks fine to me.  Except that I'd like to know why this has to be 
> done - is it something common to all DVI displays, or something you got 
> hint on from Matrox, or ... ?

I believe it is common to all systems where the initialization code (BIOS, 
FCODE, etc.) doesn't leave the card in a completely viable state.  It's not a 
DVI-specific thing in that I still can't get any DVI signals, but it does appear 
from my tests that this line is the most significant line in the patch:

+                matroxfb_DAC_out(PMINFO M1064_XDVICLKCTRL, 0);

And, I got some hints from Matrox.  :-)
-- 
Regards,
Paul Clarke


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

           reply	other threads:[~2006-04-13  0:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <443D70A7.8020702@vc.cvut.cz>]

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=443D9714.3070300@us.ibm.com \
    --to=pc@us.ibm.com \
    --cc=idr@us.ibm.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=vandrove@vc.cvut.cz \
    /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.