-
-
Notifications
You must be signed in to change notification settings - Fork 88
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.
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
V4L2_BUF_FLAG_LAST is set and epipe is returned #76
Comments
All the buffer operations are done here. It would be necessary to see in which of those operations they want that flag to be added. Anyway, it seems that it will be patched in the kernel (as I understand), so patching it in my code does not seems to be that much necessary. |
what might be the patch here if the kernel is too old, and cannot be easily updated? thanks! |
You can see here a list of all kernel versions maintained by the Linux developers, those are the only versions supported by akvcam, all those versions will receive the patch soon or later, and you are most probably using one of those kernels right now, if not just upgrade your system, also v4l2-compliance isn't reporting any bug in the driver, so this is most probably an edge case, therefore, there is not any reason to care about that patch. Also, didn't figured until now but
That bug was patched 5 years ago. Again there is not any reason to care about. |
I am not sure why I still see epipe error then. |
Give me the code snippet that is failing, also |
This is wine read v4l2 frame.
|
It is an internal project, which I cannot share just yet.
I can test a patched akvcam version without explicit streaming_stop. ie. it just starts on module init, and we never call stop in any case. I am not sure how to do that yet. |
Ok, but did you tried running a working program like ffmpeg/ffplay, or a working code example to discard a bug in your code?
What you expect to happen by removing a key function? if the program have a bug, you must fix the but, not removing code at random expecting the code to be fixed magically. |
https://patchwork.kernel.org/project/linux-media/patch/[email protected]/
I wonder whether we could skip this flag to avoid epipe errors.
The text was updated successfully, but these errors were encountered: