> Thanks to everyones help I now have a working framebuffer. > My problem was that fbcon needs to be loaded before the viafb > module (unlike the via driver, which works better with it loaded > afterwards).
Glad you've made it work (though I've had no problems with either sequence). > I can't get any joy with the built in version, all I get is a kernel > type panic. Can you provide any more information on that? Where does it panic? One thing you can try (which might be a red herring) is do 'lsmod' before and after probing the fbcon/viafb modules and making sure that when you build your all-in kernel you've marked as built-in everything that those modules would pull in. Might it be that the kernel config process doesn't know about all the dependencies? > I wasnt aware that the framebuffer driver would make alot of > difference to the speed and whats accelerated. I'm surprised it makes any difference. Is it possible that the default pixel format is different between the two framebuffer drivers? Check what 'fbset -i' and 'dfblayer' report. Colorkeyed blitting is accelerated providing the source and destination pixel formats are the same (and not otherwise). The kernel framebuffer isn't involved. Mark _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
