This might be more related to blitting, hardware acceleration and the Linux framebuffer in general, but as the answers might be interesting to other people using DirectFB, I thought I'd ask anyway.
1. When your source data is in main memory, what does hardware-accelerated blitting do differently to achieve higher performance? If the operation is just to copy data from main memory to vram, then how could this ever be "accelerated"? 2. What makes the non-accelerated framebuffer so slow anyway? At least with a vesa framebuffer, just displaying the boot-up messages seem to take way more time than the actual initialization. Where is the bottleneck, and what's done differently in the accelerated case? 3. Is it possible to do a "real" page-flip on just the framebuffer device without hardware acceleration, or will this just be implemented by copying data from one region to another? Thanks!
_______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
