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

treewide: Import and enable v4l2loopback #14

Open
wants to merge 4 commits into
base: halium-9.0
Choose a base branch
from

Conversation

fredldotme
Copy link
Contributor

This kernel module allows a virtual v4l2 device to be used by apps which make use of
v4l2 directly. In combination with a bridging daemon it it possible to enable access to the
Android camera for the Ubuntu Touch web browser as well as others applications.

@JamiKettunen
Copy link
Contributor

This is nice, but wouldn't it be better to consider looking into DKMS so this works on all supported devices and doesn't have to be manually supported on a per-device basis? I suppose even with the correct kernel headers installed that might pose a problem though with the read-only design of Ubuntu Touch sadly, so this might be the only way for now :/

@fredldotme
Copy link
Contributor Author

No, this PR has been made after careful consideration after all.

There is no possibility to ship kernel headers for all Ubuntu Touch devices and have DKMS
build all sources with every upgrade from within a recovery-based update mechanism.

Allow the kernel module to send hints to userspace, via reading
the v4l2loopback control device, regarding access of v4l2 device nodes.

This will allow frame producers to determine when to pause production
or to show permission dialogs on behalf of the camera bridge system.
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

Successfully merging this pull request may close these issues.

2 participants