Hi Sourath, > 1. This could be obvious but still, while a thread obtains the hardware > Lock and uses OpenGL APIs on a surface (with EGLContext), is it possible > that DirectFB APIs can be used to render on the same surface concurrently?
No. > Does the "Lock" function (b)lock the surface access from other threads? Yes. > 2. If the surface/layer is double buffered, then to make the drawings > rendered by OpenGL APIs visible we need to call IDirectFBSurface::Flip? Yes. > This technically means that a module that does the OpenGL rendering has > to return the control to the one handling DirectFB APIs to make the > drawings visible - is that the case really? Yes. The IDirectFBGL interface allows the OpenGL/OpenGL ES APIs to be used to render on DirectFB's surfaces, thus it retains flipping control (which may even by done using EGL pixmap surfaces instead of EGL window surfaces to provide support for hiding/showing the front buffer as required by the IDirectFBScreen interface's cool 'n clean mixer display layer visibility functionality). Cheers, Timothy -- Timothy Strelchun CE Software Engineering Digital Home Group Intel Corporation The views expressed above are my own and not those of Intel _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
