Here is another set of DirectFB 1.0.1 improvements. People may find these useful for developing a custom non-framebuffer systems driver that handles management of video memory based visible and non-visible surfaces. I believe the need to make some of these changes probably led to the introduction of the surface pools in version 1.2.x.
Patch "1-Added_SurfaceBufferFieldForDriverSpecificData.diff":
1. Added a _SurfaceBuffer field to hold a driver-specific
data pointer. Useful for obtaining custom surface data
specifically associated with the individual surface
buffer.
Patch "2-DriverCanAllocateNonVisibleSurfaces.diff":
2. Systems drivers can now manage non-visible surfaces
allocated as video memory. Required the addition of two
new core system functions that a driver must provide
(VideoMemoryAllocate and VideoMemoryDeallocate). If
they are not needed and the DFB core software should
manage allocation as usual, the functions should
return DFB_UNIMPLEMENTED from both functions.
Patch "3-RemoveRegionCoreSurfaceParameter.diff":
3. Added parameter to the DisplayLayerFuncs::RemoveRegion
function prototype for a CoreSurface pointer. It is
necessary to provide the display layer's CoreSurface to
the systems driver so that it can fully perform region
removal and reverse the actions performed by the
SetRegion function (such as deallocating the underlying
resources associated with surface such as an EGLSurface).
Regards,
Timothy
--
Timothy Strelchun
CE Software Engineering
Digital Home Group
Intel Corporation
The views expressed above are my own and not those of Intel
1-Added_SurfaceBufferFieldForDriverSpecificData.diff
Description: 1-Added_SurfaceBufferFieldForDriverSpecificData.diff
2-DriverCanAllocateNonVisibleSurfaces.diff
Description: 2-DriverCanAllocateNonVisibleSurfaces.diff
3-RemoveRegionCoreSurfaceParameter.diff
Description: 3-RemoveRegionCoreSurfaceParameter.diff
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
