[PATCH v4 02/14] Documentation: media: description of DMABUF importing in V4L2

Marek Szyprowski m.szyprowski at samsung.com
Mon Apr 23 00:50:05 PDT 2012

Hi Mauro,

On Friday, April 20, 2012 3:37 PM Mauro Carvalho Chehab wrote:


> >> So my rough-idea was to remove USERPTR support from kernel
> >> drivers (if possible of course) and to provide an emulation
> >> layer in the userspace code like libv4l2.
> >>
> >> Please note that it is only a rough idea. Just brainstorming :)
> > It is *too early* to start any discussion on this topic.
> > Especially until DMABUF is mature enough to become a good
> > alternative for userptr.
> Looking at the hole picture, dropping USERPTR would only make
> sense if it is broken on dev2user (or user2dev) transfers.
> Dropping its usage on dev2dev transfers makes sense, after having
> DMABUF implemented.
> Yet, if some userspace application wants to abuse of USERPTR in order
> to use it for dev2dev transfer, there's not much that can be done at
> Kernel level.
> It makes sense to put a big warn at the V4L2 Docs telling that this
> is not officially supported and can cause all sorts of issues at
> the machine/system.

Please note that all current drivers which use videobuf/videobuf2-dma-contig
are able to use userptr memory access method only with physically contiguous
memory. This means that in fact they work only buffers, which come from other
devices and dev2dev transfers are the only possibility. malloc()ed memory
buffers are rejected.

Best regards
Marek Szyprowski
Samsung Poland R&D Center

More information about the dri-devel mailing list