[Linux-fbdev-users] voodoo 5 framebuffer (on Alpha) @ high pixclocks

[Jurriaan on A. <thu...@xs...>]

I'm having trouble getting my voodoo 4500 pci working correctly on my
Alpha (kernel 2.4.17pre2).

If I use the stock-kernel, and specify
'video=tdfx:1600x1200-16@75,nohwcursor', my Eizo F930 switches off.
XFree works perfectly in 1600x1200-16@80.

If comment out this part:

#if 0
  if(freq > i->max_pixclock/2) {
    freq = freq > i->max_pixclock ? i->max_pixclock : freq;
    reg.dacmode |= DACMODE_2X;
    reg.vidcfg  |= VIDCFG_2X;
  }
#endif

it works, but I have a feeling I'm running out-of-spec now. 

So I downloaded the latest patch, 3dfx-20010507, and it doesn't work at
all. The system boots, but the screen stays black. I enabled debugging,


udf: registering filesystem
fb: tdfxfb_probe: PCI memory enabled. name=Voodoo 5 noinit=1
fb: tdfxfb_probe: fb: Voodoo 5 memory = 65536K
fb: tdfxfb_switch_con: start with fb Voodoo 5 pdsp=fffffc00001fc280 dsp=fffffc0000b13800 prevcon=-1 con=0
fb: tdfxfb_switch_con: start with fb Voodoo 5 pdsp=fffffc0000b13800 dsp=fffffc0000b13800 prevcon=0 con=0
fb: do_set_par: wrregs: vidcfg:04040483,dacmode:00000001,vidpll:00006114,freq:0003170f
Console: switching to colour frame buffer device 133x54
fb0: 3Dfx Voodoo 5 frame buffer device, 65536K @ 0x18000000
pty: 256 Unix98 ptys configured

and nothing looks wrong there. In fact, the vidcfg / dacmode values are
exactly the same as for the standard kernel, except for DACMODE_2X and
VIDCFG_2X.

If I comment out the DACMODE_2X/VIDCFG_2X part in the 20010507-driver,
the kernel crashes on boot.

Any hints on how to proceed? I've sent mail to the maintainers already,
BTW. No reaction so far, but it's only been 2 days or so.

Thanks,
Jurriaan
-- 
Linux hackers are funny people: They count the time in patchlevels.
	Gerd Knorr
GNU/Linux 2.4.17-pre2 on Debian/Alpha 64-bits 990 bogomips load:0.00 0.03 0.04