Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

support for VIDIOC_*_PRIORITY #67

Closed
umlaeute opened this issue Jun 17, 2014 · 0 comments
Closed

support for VIDIOC_*_PRIORITY #67

umlaeute opened this issue Jun 17, 2014 · 0 comments
Labels
kind:bug pending v4l2-compliance

Comments

@umlaeute
Copy link
Owner

v4l2-compliance complains:

VIDIOC_G_PRIORITY returned -1 (Inappropriate ioctl for device)
fail: v4l2-compliance.cpp(393): doioctl(node, VIDIOC_G_PRIORITY, &prio)
test VIDIOC_G/S_PRIORITY: FAIL
umlaeute added a commit that referenced this issue Jun 17, 2014
@umlaeute
set VIDEO_M2M capabilities
35a59da 
github Fixes #67
vicamo added a commit to vicamo/v4l2loopback that referenced this issue Mar 13, 2021
@vicamo
stop declaring V4L2_CAP_VIDEO_M2M capability
6884a81 
v4l2-compliance complains about "Video Capture cap set, but no Video
Capture formats defined" because V4L2_CAP_VIDEO_M2M is set and yet
vidioc_enum_fmt_cap implementation would simply return -EINVAL before
being ready for capturing.

V4L2 memory-to-memory operatons have never been actually supported. It
was introduced in an attempt to fix umlaeute#67,
VIDIOC_G/S_PRIORITY test failures reported by v4l2-compliance, but
VIDIOC_G/S_PRIORITY is an exclusive feature when V4L2 file handle
framework is used, and this was certainly not the case until
umlaeute#345 that brought in v4l2_fh for V4L2 Event API
support.

This change removes all declarations of M2M support.

Signed-off-by: You-Sheng Yang <vicamo@gmail.com>
vicamo added a commit to vicamo/v4l2loopback that referenced this issue Mar 13, 2021
@vicamo
compliance: stop declaring V4L2_CAP_VIDEO_M2M capability
9a77eb6 
v4l2-compliance complains about "Video Capture cap set, but no Video
Capture formats defined" because V4L2_CAP_VIDEO_M2M is set and yet
vidioc_enum_fmt_cap implementation would simply return -EINVAL before
being ready for capturing.

V4L2 memory-to-memory operatons have never been actually supported. It
was introduced in an attempt to fix umlaeute#67,
VIDIOC_G/S_PRIORITY test failures reported by v4l2-compliance, but
VIDIOC_G/S_PRIORITY is an exclusive feature when V4L2 file handle
framework is used, and this was certainly not the case until
umlaeute#345 that brought in v4l2_fh for V4L2 Event API
support.

This change removes all declarations of M2M support.

Signed-off-by: You-Sheng Yang <vicamo@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind:bug pending v4l2-compliance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@umlaeute