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
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?
The text was updated successfully, but these errors were encountered:
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
Packaging/architecture questions here:
droidcam
require it's own kernel module? From security point of view, this seems suspicious, that application brings it's own kernel module.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?The text was updated successfully, but these errors were encountered: