From: "Ville Syrjälä" <syrjala@sci.fi>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Another problem, seemingly coming f
Date: Wed, 16 Oct 2002 11:59:56 +0300 [thread overview]
Message-ID: <20021016115956.A8311@sci.fi> (raw)
In-Reply-To: <4BECCE234BB@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Wed, Oct 16, 2002 at 09:00:27AM +0200
On Wed, Oct 16, 2002 at 09:00:27AM +0200, Petr Vandrovec wrote:
> Ah, these ones... What pixclocks do you use? It is like if CRTC2 has
> not enough memory bandwidth available, and so it displays stale data.
Can the CRTC high priority stuff affect this? Does matroxfb touch the
priority registers?
> Only problem I can think of is that system VCO frequency is always set
> to 133333 kHz (for G100/200/400) in matroxfb_DAC1064.c. Your PINS
> suggest that 200MHz are correct system clocks for your chip.
What do you think about making matroxfb do clock setup accrding to PINS?
XFree86 mga driver does it own clock setup but DirectFB matrox driver
does not. I'm pretty sure increasing the clocks would provide some
speed benefits since the BIOS default clocks are pretty low.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
next prev parent reply other threads:[~2002-10-16 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 7:00 Another problem, seemingly coming f Petr Vandrovec
2002-10-16 8:59 ` Ville Syrjälä [this message]
2002-10-16 10:16 ` Carlo E. Prelz
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 14:25 Petr Vandrovec
2002-10-16 18:40 ` Ville Syrjälä
2002-10-15 15:36 Petr Vandrovec
2002-10-15 10:59 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=20021016115956.A8311@sci.fi \
--to=syrjala@sci.fi \
--cc=VANDROVE@vc.cvut.cz \
--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).