Quoting Neil Radisch ([EMAIL PROTECTED]): > I've had a good deal of trouble with this patch. I've applied it to two > different systems. > > 1) P2 - 400mhz with 2.4.19 kernel and a Matrox G400 > 2) P4 2.4Ghz with 2.4.20 kernel and a Matrox G550 > > In both cases enabling the 32Mb stuff causes the framebuffer to periodically > go > blank (or get filled with junk). Eventually the text display returns after > sufficient > stuff has scrolled by. The effect is periodic, making me think that when the > upper > memory starts being used something gets funky and the screen goes berserk.
The problem is that the matroxfb developers didn't use the DSTORG and SRCORG registers but treat the whole video memory as one surface with x/y coordinates. However, the y coordinate register YDSTLEN doesn't allow such large surfaces. So it's just a little effort to get matroxfb running without glitches on 32mb. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
