Hi,

in our video conference application the grabbing (QBUF, DQBUF) is done 
in a separate thread. The main thread is responsible for the user 
interface and queries the controls, input and current standard values 
from time to time.

With the latest uvc driver (r217) and vanilla Linux 2.6.25.6 I've 
noticed the strange behavior that the grabbing thread hangs in the DQBUF 
ioctl. If I remove the control queries from the gui thread everything is 
working fine. After the first hang of the driver, even luvcview hangs at 
the buffer operation.

With the bttv driver everything works fine. I'll test vivi and pwc 
driver later.

My systems are a i686 and one amd64 system with one Logitech 9000 and 
one Microsoft NX-6000. I've tried to create a simple testcase, but 
suprinsingly this testcase works fine.

Can I enable more logging than setting the trace parameter to 0xfff?
Have you any idea what went wrong here? Is the V4L2-API designed to be 
thread safe?

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

Reply via email to