Hi Lars, On Wednesday 26 September 2007, Lars Täuber wrote: > Good evening Laurent, > > > Could you please post the output of > > > > lsusb -v -d 0474:0238 > > of course: > $ lsusb -v -d 0474:0238
Thanks. > Bus 001 Device 004: ID 0474:0238 Sanyo Electric Co., Ltd > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 239 Miscellaneous Device > bDeviceSubClass 2 Common Class > bDeviceProtocol 1 Interface Association > bMaxPacketSize0 64 > idVendor 0x0474 Sanyo Electric Co., Ltd > idProduct 0x0238 > bcdDevice 1.00 > iManufacturer 1 > iProduct 2 > iSerial 3 [snip] That's a new one. I havent seen that webcam before. It might be based on a new chipset. I'm afraid there's not much I can do. The camera doesn't define any control, so we can't test them to see if the camera is still somehow alive after the first luvcview run. I suspect either a timing issue, or more probably some kind of firmware bug not triggered by Windows. The Windows driver might send an optional command to the webcam when stopping the stream, and failing to send that command might trigger a bug. Would you be able to get a USB trace when the webcam is plugged in a Windows box ? Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
