On 06/02/2011 08:23 PM, Strelchun, Timothy wrote:
Surprise! I stumbled upon the need for a fourth patch I had missed (our custom development branch did not have a general solution implemented for graphics drivers to report full support for system memory based surfaces using the CCF flags yet).Here are the details from this FOURTH patch: ----------------------- Subject: [PATCH] Updated dfb_gfxcard_check_state to check for full system memory support. Added CCF_WRITESYSMEM so that a graphics driver can fully report that it supports reading and writing to system memory based surfaces, and updated the dfb_gfxcard_check_state function to use that data to determine if acceleration is possible when the back buffer policy is system only. ----------------------- Regarding usage: With these four patches, for a UMA-based graphics driver to support system memory surface (and preallocated ones) it just needs to make the following call from the driver_init_driver function: dfb_surface_pool_gfx_driver_update( CSTF_INTERNAL | CSTF_PREALLOCATED, CSAID_GPU, CSAF_READ | CSAF_WRITE ); and from the driver_init_device function add support for reading and writing system memory surfaces to the flags already specified: device_info->caps.flags |= CCF_READSYSMEM | CCF_WRITESYSMEM; Then make sure the driver handles all of the different types of surface buffers and allocations that it will receive in the CheckState and SetState functions.
First one's pushed, thanks! -- 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
