Once the patch is installed recompile DirectFB so the DirectFB Savage driver gets built. It took be a while to figure out that the configure script won't build the Savage driver unless it can see that the kernel has been patched to include the Savage framebuffer. In practise this means making sure the include files for your patched kernel are copied to /usr/include/linux
I'm running Debian stable with a standard Linus kernel. I guessing the main difference between the KM266 and the P4M266 is support for AMD/Intel chips respectively.
Give the above a try, use df_dok (one of the examples) to benchmark the system before and afterwards and you'll soon know whether the h/w acceleration is being used.
Let me know how you get on. I'm happy to answer further questions.
Regards,
Ben.
Maciej Arteria wrote:
Ben Lamb, Thank you for replay.
What framebuffer driver did have you been using? The one from linux distribution or from hw vendor.
What I know KM266 and P4M266 have the same vga chip - ProSavage 8 (sometimes called diffrently by resellers). If you were able to manage that then I should .
Let us know how did you managed it to work.
May be there is a path to solve hung problem.
I am looking forward..,
Regards,
Maciej
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
