Shachar Kaufman wrote: > On Wed, Nov 12, 2008 at 3:57 PM, Niels Roest <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > Shachar Kaufman wrote: > > Thanks Niels, you answers shed a lot of new light on the topics I've > been confused about. > Let me see if I got this straight now: > > We're getting there :) > > OK, great! > > I wanted to ask and forgot: > > 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. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users