> >> The zero step size for the absolute exposure time is obviously wrong. I
> >> don't currently have my USB analyzer to check what's going on there.
>
> I found the problem in the driver. There is a bug in the uvc_get_le_value
> function, which leads to wrong values when reading 32-bit wide controls. I
> have a patch and I'll submit it to Laurent. The control now looks as
> follows:
>
> Exposure (Absolute)
> ID : 17,
> Type : Dword,
> Flags : { CAN_READ, CAN_WRITE, IS_CUSTOM },
> Values : [ 1 .. 10000, step size: 1 ],
> Default : 166
>
> >> Also, I get errors when I try to read these controls. This seems to be
> >> why the
> >> controls don't work in luvcview.
>
> Another bug in the control definition in the UVC driver. Certain controls
> were accidentally marked as write-only, which explains the error. It's
> part of the patch that I mentioned, it should be fixed soon in the
> repository.
>
> > Yes luvcview used the step value.
>
> We'll post a message to the list as soon as the patch is committed. It
> would be great if you could retest it ...
This should now be fixed. Happy testing :-)
Laurent Pinchart
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
