From: Petr V. <VAN...@vc...> - 2002-10-16 14:25:44
|
On 16 Oct 02 at 11:59, Ville Syrj=E4l=E4 wrote: > 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? Yes, matroxfb sets them to default values, recommended for low pixclock rates. You must set them when you initialize hardware after poweron. > > 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. I'll not use other clocks than specified in the BIOS (BIOS uses value specified in PINS). It is highest rate Matrox says to use. That Matrox windows drivers use higher frequency is another story: they have access to other information than I have, and so they can select highest system clock from chip revision, serial number and other values... On G450/G550 I use frequency specified in BIOS PINS. G400 (and older) historically used hardwired values in matroxfb, and because of I do not use them regulary anymore, I try to not touch their initialization code (and as you can saw, even then I had mistake in G400 initialization... unfortunately testing powerup initialization requires plugging in another videocard, unplugging powercord, and then trying again and again...). If you'll cook and test patch which will set system clocks on G400 according to the value specified in the BIOS, or if you'll create patch which will add ioctl() or some other operation to set system PLL, I'll apply it without problem (if code is correct, changing system PLL is not trivial operation). Petr Vandrovec van...@vc... |