I now see there's a CoreSurfacePoolDescription.priority field. The system registers as CSPP_DEFAULT, when davinci's gfxdriver managers are registered as CSPP_PREFERED.
On Thu, Nov 13, 2008 at 10:07 AM, Denis Oliver Kropp <[EMAIL PROTECTED]>wrote: > 4. when I register my surface pool manager, how does DFB make use of both >> this new manager and the one the system (e.g. devmem) registered at startup? >> moreover I saw in the only driver that does this kind of thing (davinci) >> that you can register more than one manager - how are the managers managed? >> (no pun intended) >> > > Up til 1.3.x the negotiation was quite simple, trying to match surface caps > and types along with the access (CPU/GPU r/w) against the pool information, > but with a TestConfig() call as a last check at the pool. > > For 1.5.x the mechanisms have been improved further. >
_______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
