On 6.6.2008, at 13.14, Juho Vähä-Herttua wrote:
because I also get it for nonexistant controls. By the spec PU_WHITE_BALANCE_COMPONENT_AUTO_CONTROL should also support the commands SET_CUR, GET_CUR, GET_INFO, GET_DEF so I tried to do GET_INFO and

I meant PU_WHITE_BALANCE_TEMPERATURE_AUTO_CONTROL but the definitions are the same in both anyway...

Now how do you think, is the camera faulty with reporting the White Balance Temperature, Auto or is there still something that could be done? If it's considered to be faulty I can add a hack to ignore the white balance thing for this camera type and test it...

I made a patch that adds UVC_QUIRK_IGNORE_WBTA definition and ignores the mentionied control in as early stage as possible so that it makes sense. In this case that means ignoring it at uvc_ctrl_add_ctrl when the device supported controls are added to the internal list updated by the driver. Works for me and doesn't affect any other devices, but if there's some evidence that this uglyish hack can be avoided, that would be naturally great.

I hope Lorenzo could also check that this fixes his gstreamer problem, I am still having problems with Ekiga but they are unlikely to be related to this problem.


Regards,

Juho


Attachment: sigma_quirk.diff
Description: Binary data




Attachment: PGP.sig
Description: This is a digitally signed message part

_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Reply via email to