On 05/15/2011 12:35 PM, Strelchun, Timothy wrote:
-----------------------2 of 3
Subject: [PATCH] Added buffer alloc destroy notify message.
Added a surface notification message sent for each buffer allocation
that is destroyed. It is sent by the dfb_surface_pool_deallocate
function using a new notify function called dfb_surface_pool_notify.
A graphics driver that allocates custom shared/local resources for a
buffer allocation from any surface pool (such as the pre-allocated
memory one) should register to receive this new buffer allocation
destruction message. This will give the graphics driver (in each
registered process) an opportunity to destroy those associated custom
shared/local resources.
I'm starting to work through your patches, finally :)
Have you seen that CoreSurfaceBuffer is a FusionObject now. It can be
decoupled from the surface meaning the back pointer becomes NULL, any
Deallocate or Unlock may never rely on a valid 'surface' pointer in
a buffer.
I have done the same with the allocations, so CoreSurfaceAllocation
is a FusionObject as well, but I haven't committed that yet.
We need to put the surface_data pointer into the CoreSurfaceAllocation
then.
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
