Hi Denis, Thanks for your clarification.
Question may be out-of topic. Is there any illustration/document available to understand DFB's multi application core architecture?. On 19 December 2012 16:30, <directfb-users-requ...@directfb.org> wrote: > Message: 1 > Date: Tue, 18 Dec 2012 18:07:49 +0100 > From: Denis Oliver Kropp <d...@directfb.org> > To: directfb-users@directfb.org > Subject: Re: [directfb-users] Async Blitting/Filling in DFB.. > Message-ID: <50d0a2e5.5060...@directfb.org> > Content-Type: text/plain; charset=ISO-8859-1 > > On 12/11/12 09:35, Arunprasad Rajkumar wrote: > > Hello Developers, > > > > How directfb implements blitting/filling ? As sync call or async call or > it is gfx driver dependent? > > > > Graphics drivers can queue the operations. When synchronisation is > required, the core calls the driver's > EngineSync() function to make sure all pending operations are finished. > > In DirectFB 1.7 there is a new task manager architecture that manages > multiple async running cores with > synchronisation based on the buffers being accessed, without blocking any > thread at any time, like EngineSync() > does for example with application threads on flipping. > > -- > Denis Oliver Kropp > DirectFB integrated media GmbH > > > > -- *Arunprasad Rajkumar* http://in.linkedin.com/in/ararunprasad
_______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
