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.

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

Use v4l2loopback upstream kernel module #56

Closed
invidian opened this issue May 11, 2020 · 1 comment
Closed

Use v4l2loopback upstream kernel module #56

invidian opened this issue May 11, 2020 · 1 comment

Comments

@invidian
Copy link
Contributor

Packaging/architecture questions here:

  • Why does droidcam require it's own kernel module? From security point of view, this seems suspicious, that application brings it's own kernel module.
  • Why upstream https://github.com/umlaeute/v4l2loopback couldn't be used? I think this would simplify the maintenance work, as well as packaging, as v4l2loopback is already available for several distros (e.g. Arch, Ubuntu). Are there some specific changes done to this module, which e.g. has been rejected by upstream?
@aramg
Copy link
Collaborator

aramg commented May 11, 2020

v4l2loopback was forked in 2013 for droidcam, primarily because:
(1) I wanted the webcam to report itself as "DroidCam" for UX
(2) I wanted the webcam to work (be blank) even if the client isnt running
(3) Back then v4l2loopback wasn't as widely available IIRC

I'm open to deprecating this old fork, especially if v4l2loopback get accepted into the kernel
umlaeute/v4l2loopback#268 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants