[Piglit] [v7 02/12] framework: support for creating dma buffers through libdrm

Chad Versace chad.versace at linux.intel.com
Mon Jun 3 17:18:10 PDT 2013

On 05/28/2013 02:51 AM, Topi Pohjolainen wrote:
> In order to test EXT_image_dma_buf_import one needs the capability
> of creating driver specific buffers. By probing the environment for
> drm libraries one can decide for which drivers the support is to
> be built.
> v2 (first five according to Chad's advice):
>     - replace manual search for drm with 'pkg_check_modules()'
>     - move BATCH_SZ into intel specific part
>     - use ARRAY_SIZE
>     - fix faulty check for mem-allocation (drm_buf vs. buf)
>     - define the opaque type piglit_dma_buf declared in platform
>       independent interface instead of introducing new local type
>       (piglit_drm_dma_buf)
>     - use 'drm_intel_bo_subdata()' instead of mapping the buffers
>       for CPU
>     - also set the support for GBM in addition to X11
> v3:
>     - fix a type (does -> doesn't)
>     - exclude intel driver entry points when the driver is not
>       present
> v4:
>     - introduce checking for the libdrm base in the top level of
>       the build system. This can be then used to control the
>       compilation of the invidual tests as well.
>     - add the hooks for all the supported configurations in the
>       same place (piglit_gl_framework_init()) instead of one by one
>       locally (Chad)
>     - added destruction hook NULL pointer support (Chad, Ken)
>     - set the file descriptor to zero before exporting (Chad)
> v5 (Eric):
>     - use 'bool' instead of "zero for success, non-zero for failure"
> Signed-off-by: Topi Pohjolainen <topi.pohjolainen at intel.com>
> Reviewed-by: Eric Anholt <eric at anholt.net>

Reviewed-by: Chad Versace <chad.versace at linux.intel.com>

More information about the Piglit mailing list