v4l2: camera: Handle memory mapping of buffers directly
In the upcoming FrameBuffer API the memory mapping of buffers will be left to the user of the FrameBuffer objects. Prepare the V4L2 compatibility layer to this upcoming change to ease conversion to the new API. Signed-off-by: Niklas Söderlund <niklas.soderlund@ragnatech.se> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
This commit is contained in:
@@ -223,7 +223,7 @@ void *V4L2CompatManager::mmap(void *addr, size_t length, int prot, int flags,
|
||||
if (!proxy)
|
||||
return fops_.mmap(addr, length, prot, flags, fd, offset);
|
||||
|
||||
void *map = proxy->mmap(length, prot, flags, offset);
|
||||
void *map = proxy->mmap(addr, length, prot, flags, offset);
|
||||
if (map == MAP_FAILED)
|
||||
return map;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user