Lucian Muresan wrote: > Jason Tackaberry wrote: >> On Fri, 2007-01-12 at 23:31 +0800, mike lewis wrote: >>> Before I go off to bed I just have to say that I figured out what the >>> issue was. vidix wasn't detecting the RAm size of my card. So I hard >>> coded the RAM size (from 16 to 32) and now there is not more artifacts >>> on the screen. >> >> Where did you hardcode this? > > I think the proper way is not to hardcode it, but to apply the so-called > "matroxfb-full-memory" kernel patch. Another useful patch might be the > one called "matroxfb-g400-clock", I don't know why they haven't made it > into the kernel for such a long time. You can find older versions of > them in the 'patches' directory of the DirectFB source, and I guess they > apply to recent kernels too, or you can easily adapt them by hand. If > you prefer, you can use mine attached in this message, already adapted > for 2.6.18 (should also apply to 2.6.19), the one called > linux-2.6.18_matroxfb-address-ioctl_v3.diff is necessary for newer > versions of DirectFB.
I wouldn't use the "matroxfb-g400-clock" patch, Villi recommended to use it and I tried it recently and it fucked up the driver big time. May be it depends on the card a bit, mines a DH with sdram. The "matroxfb-full-memory" is good though. Duncan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
