I am writing a new GFX driver as indicated before. The System has more than one framebuffer and I want to be able to use both.
I decided to look at how the davinci driver does this. It uses the 'devmem' system. However the driver provides functions for allocation / deallocation of surfaces, joining and leaving the surface pool etc. The problem is that it only seems to allow for allocation of surfaces on a layer and a layer id of 0. I cannot see what it does when this is not the case. i.e What happens when you create an offscreen surface using the davinci driver? I am new to this but i think that I need to extend the AllocateBuffer function in the davinci driver to cope with what to do when the surface type is not LAYER or layer id is not 0. Am I correct. Where will an offscreen surface get allocated for the davinci driver i.e if you run df_andi where do the offscreen surfaces get allocated? I can't find where! Cheers Dan -- View this message in context: http://www.nabble.com/Writing-a-new-GFX-driver.-tp14619900p14619900.html Sent from the DirectFB Dev mailing list archive at Nabble.com. _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
