kmssink: use drm bufferpool and dmabuf to for zero copy
authorRob Clark <rob@ti.com>
Tue, 12 Jun 2012 15:19:26 +0000 (10:19 -0500)
committerRob Clark <rob@ti.com>
Thu, 14 Jun 2012 00:31:25 +0000 (19:31 -0500)
commitaf3d0118cc55415fadd06ab2419febfc0be83c48
tree577e376ce1ee3b622106ea5efabd989e7a8aecdb
parente8f2dd77e927d5753966d6d54a4864a108d47ca4
kmssink: use drm bufferpool and dmabuf to for zero copy

Get rid of our internal buffer pool, and instead use GstDRMBufferPool.
Use dmabuf to get handle to underlying buffer object, and qdata to
attach our own private data to the buffer.

This way we don't really care who allocates the buffer, and can deal
in the same way with our own buffers, or any other buffer allocator
that is using dmabuf.
14 files changed:
sys/kms/Makefile.am
sys/kms/gstducati.h [deleted file]
sys/kms/gstducatibuffer.c [deleted file]
sys/kms/gstducatibuffer.h [deleted file]
sys/kms/gstducatibufferpool.c [deleted file]
sys/kms/gstducatibufferpool.h [deleted file]
sys/kms/gstducatidrmbuffer.c [deleted file]
sys/kms/gstducatidrmbuffer.h [deleted file]
sys/kms/gstducatikmsbuffer.c [deleted file]
sys/kms/gstducatikmsbuffer.h [deleted file]
sys/kms/gstkmsbufferpriv.c [new file with mode: 0644]
sys/kms/gstkmsbufferpriv.h [new file with mode: 0644]
sys/kms/gstkmssink.c
sys/kms/gstkmssink.h