For me dmabuf and cenalloc offer two different features: one is buffer
sharing (dmabuf) and one is buffer allocation (cenalloc).
You may want to use dmabuf sharing feature whithout need of the buffer
allocation feature, that is what for drm, v4l2, ION and other use
dmabuf.
In addition of dmabuf
Hi Daniel,
Thanks a bunch for your review comments! A few comments, post our
discussion at LPC;
On 12 October 2014 at 00:25, Daniel Vetter dan...@ffwll.ch wrote:
On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
At present, struct device lacks a mechanism of exposing memory
access
On Wed, Dec 10, 2014 at 07:01:16PM +0530, Sumit Semwal wrote:
Hi Daniel,
Thanks a bunch for your review comments! A few comments, post our
discussion at LPC;
On 12 October 2014 at 00:25, Daniel Vetter dan...@ffwll.ch wrote:
On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
On 10/11/2014 11:55 AM, Daniel Vetter wrote:
On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
At present, struct device lacks a mechanism of exposing memory
access constraints for the device.
Consequently, there is also no mechanism to share these constraints
while sharing buffers
On Mon, Oct 13, 2014 at 01:14:58AM -0700, Laura Abbott wrote:
On 10/11/2014 11:55 AM, Daniel Vetter wrote:
On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
At present, struct device lacks a mechanism of exposing memory
access constraints for the device.
Consequently, there is
On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
At present, struct device lacks a mechanism of exposing memory
access constraints for the device.
Consequently, there is also no mechanism to share these constraints
while sharing buffers using dma-buf.
If we add support for
At present, struct device lacks a mechanism of exposing memory
access constraints for the device.
Consequently, there is also no mechanism to share these constraints
while sharing buffers using dma-buf.
If we add support for sharing such constraints, we could use that
to try to collect
