Kristoffer Koch
2016-03-10 08:56:49 UTC
Hi,
We're developing a USB UVC camera, and created an extension unit for
tuning various settings in our image pipeline.
Our descriptor is listed with lsusb as
VideoControl Interface Descriptor:
bLength 27
bDescriptorType 36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 4
guidExtensionCode {29c8acf6-dbac-11e5-8424-f39068f75511}
We tried adding the controls to v4l with uvcdynctrl, but only got
ENOENT (which is a strange error code to get when no files are
involved). We instrumented uvc_ctrl.c with some traces, and found out
that while lsusb lists our guid as above, the kernel compares against
f6acc829-acdb-e511-8424-f39068f75511, which seems like an endianess
issue.
It could be an issue with uvcdynctrl, but for me it seems like a
kernel issue, as the parameter sent from uvcdynctrl is printed
correctly in the kernel log.
Anyway, many thanks to the linux community for letting us have a very
pleasant platform for developing hardware on.
Best regards,
We're developing a USB UVC camera, and created an extension unit for
tuning various settings in our image pipeline.
Our descriptor is listed with lsusb as
VideoControl Interface Descriptor:
bLength 27
bDescriptorType 36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 4
guidExtensionCode {29c8acf6-dbac-11e5-8424-f39068f75511}
We tried adding the controls to v4l with uvcdynctrl, but only got
ENOENT (which is a strange error code to get when no files are
involved). We instrumented uvc_ctrl.c with some traces, and found out
that while lsusb lists our guid as above, the kernel compares against
f6acc829-acdb-e511-8424-f39068f75511, which seems like an endianess
issue.
It could be an issue with uvcdynctrl, but for me it seems like a
kernel issue, as the parameter sent from uvcdynctrl is printed
correctly in the kernel log.
Anyway, many thanks to the linux community for letting us have a very
pleasant platform for developing hardware on.
Best regards,
--
Kristoffer E. Koch
Kubicam
Kristoffer E. Koch
Kubicam