Georg, The scr_fb.c driver is an “umbrella” driver that interfaces with /dev/fb0, and then loads a subdriver depending on the fb0 framebuffer format. These subdrivers have update functions, and definitely use fast blitting. This was the major focus of the rewrite I did several years ago, and remains as the HEAD in git.
The scr_mem.c driver is used much the same as scr_fb.c, except that it is only used internally for offscreen pixmap drawing, which is normally, but not always, in the format of the fb0 RAM. We now support offscreen bitmaps that are of different formats for flexibility, and scr_mem.c handles this. It also uses the same subdrivers for fast blitting. Regards, Greg > I looked at the "scr_fb.c" driver and found that it does not have an "update" > function. Does that mean that it will only write single pixels and not > support blitting? The other screen drivers usually have an update function > for that. > > Also I tried to use the "scr_mem.c" driver. This has an "fb_update" update > function and displays the screen ok based on the "/dev/fb0" device. The > mouse, however, is still displayed as a text mode mouse and I did not get it > to work. How can I get this screen driver to work properly with the > framebuffer device? > > Georg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org > For additional commands, e-mail: nanogui-h...@linuxhacker.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org For additional commands, e-mail: nanogui-h...@linuxhacker.org
