>>> does the uvcvideo module export some controls that can be set via the
>>> sysfs filesystem? I'm looking for a way to toggle the status LED on and
>>> off. Or is this directly controlled my the hardware?
>>>
>>> My cam is the Logitech QuickCam Sphere MP.
>
> The LED is directly controlled by the hardware. There is no way to turn
> it on or off from the computer.
>
> What Laurent said is partially true, the LED is by default controlled by
> the hardware. However, there is a way of influencing the behavior of the
> LED. There is an extension unit control that allows to set the LED to
> states like On, Off, Blinking, and Auto. The latter one is just the
> default.
If I understand correctly, things like controlling the LED are vendor specific
and should be implemented via the dynamic controls API now!? So the goal
is that the uvcvideo module just implements the UVC standard and does not
contain the code to control certain vendor specific extension units? So in the
end, there's no more need to patch and recompile uvcvideo if someone adds
some vendor specific functionality (e.g. like controlling the LED)?
I'm not sure if I understand the concept of the dynctl api correctly. Is it
correct,
that the dynctl API allows 3rd parties to register additional ioctls with the
uvcvideo module which are then available to applications?
Does the dynctl api allows this additional functionality to be exported via the
sysfs filesystem, too? Or would this require an additional sub-module e.g.
uvcvideo-logitech.ko which exports this (and only this) additional
functionality
via sysfs?
Best regards,
Jörg
Heute schon einen Blick in die Zukunft von E-Mails wagen?
www.yahoo.de/mail
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
