You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to #268, the videobuf2 api is a requirement for upstream consideration. I would like to remove support for kernels that do not support the videobuf2 api. I believe that 3.6.1 is a safe point to cut since I think it was released after the videobuf2 api landed. For the record, 3.6.1 was released in Oct 7, 2012. Removing support for prior kernels would allow the implementation of the videobuf2 api as a discrete step towards improving code quality for possible upstream acceptance while removing support only for extremely old kernels.
RFC
I would like to get feedback and see if this work is worth doing.
The text was updated successfully, but these errors were encountered:
Just so you know, I have local changes that cut kernel support at 3.6.1 and allocate, initialize, and free the vb2_queue objects. I'm currently working on migrating buffer allocation and free to the queue objects' implementations of the operations.
My environment
v4l2loopback
version: 0.12.5 (latest git)v4l2loopback doesn't implement the videobuf2 api
According to #268, the videobuf2 api is a requirement for upstream consideration. I would like to remove support for kernels that do not support the videobuf2 api. I believe that 3.6.1 is a safe point to cut since I think it was released after the videobuf2 api landed. For the record, 3.6.1 was released in Oct 7, 2012. Removing support for prior kernels would allow the implementation of the videobuf2 api as a discrete step towards improving code quality for possible upstream acceptance while removing support only for extremely old kernels.
RFC
I would like to get feedback and see if this work is worth doing.
The text was updated successfully, but these errors were encountered: