On Mon, 2013-04-22 at 21:38 +1000, Dave Airlie wrote: > On Mon, Apr 22, 2013 at 9:09 PM, Jose Fonseca <jfons...@vmware.com> wrote: > > ----- Original Message ----- > >> From: Christopher James Halse Rogers <r...@ubuntu.com> > >> > >> This is only exposed by drivers wich support the new PIPE_CAP_PRIME > >> parameter, > >> for PRIME import/export. > > > > What does exactly PIPE_CAP_PRIME entail? Please document it. > > Also why is it needed at all? > > pipe drivers should be able to render to/from any buffer the winsys > can hand it I don't think we need special treatment here, maybe just > have the generic code ask the generic kernel cap for prime support.
It's perhaps not in the right place, but I couldn't find a better one. A generic solution in the dri state tracker querying DRM_CAP_PRIME would be possible, but I think suboptimal - you really want to know if the winsys can handle dma-buf fds, and that's hidden. It's easy enough to keep PIPE_CAP_PRIME and make the pipe drivers not pull in drm.h, if that's accepable. If its not acceptable, and it's ok to lie about driver support for image v7 then I can gate it in the dri state tracker. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
