On Wed, Apr 6, 2022 at 1:16 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
On Tue, Apr 5, 2022 at 9:07 PM Demi Marie Obenour <demiobenour(a)gmail.com> wrote:
>
> On 4/5/22 16:09, Neal Gompa wrote:
> > This problem also makes life miserable for people working
with third
> > party open source kernel modules too. As a live streamer, for example,
> > I need to use v4l2loopback, which will never exist in mainline because
> > v4l2 maintainers don't like it at all.
> Are you sure about that? There is probably a better place to
talk
> about this, but Qubes OS also will be needing v4l2loopback soon (for
> Qubes Video Companion) and so I have a strong interest in getting it
> upstreamed.
>
Yes. Last I heard, V4L2 folks think it'd be used to bypass making a
real camera driver for the kernel. That's pretty much why it's not
there.
Well, I think it was mostly one person, but as
they are the primary maintainer for the subsystem
that opinion carries some weight (although it
should be noted that another co/sub-maintainer
has been somewhat more interested in getting
v4l2loopback upstreamed). However, last I knew,
there was still some significant work to be
completed on the driver in order to meet current
kernel and subsystem standards before it could
be reconsidered for inclusion. Those that want
to see the driver upstreamed should likely
contribute to those changes.