Hi Mildred,
On Tuesday 24 June 2008, Mildred wrote:
> Thanks for your answer :)
>
> Le Tue 24/06/2008 à 00:18 Laurent Pinchart à écrit:
> > bInterfaceClass should be set to '14 Video'. This means your firmware
> > hasn't been patched.
>
> Well, there are three different interface descriptors, and one of these
> have the correct bInterfaceClass:
>
> Interface Descriptor:
> ...
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> ...
> Interface Descriptor:
> ...
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> ...
> Interface Descriptor:
> ...
> bInterfaceClass 14 Video
> bInterfaceSubClass 2 Video Streaming
> bInterfaceProtocol 0
They should all have bInterfaceClass set to '14 Video'. The first interface
should have bInterfaceSubClass set to '1 Video Control' and the second to '2
Video Streaming'.
> > > Do you have any ideas about this problem ?
> > > Some months ago, my webcam worked with a driver derived from
> > > uvcvideo. but that was with the previous kernel. Now it no longer
> > > compiles.
> >
> > Try to upgrade the firmware extractor/loader. It should patch your
> > firmware to make it compatible with the UVC driver.
>
> I tried the iSight firmware tools version 1.2 with two different
> firmwares. Their MD5 sums are:
>
> 8b78709d02d3584f40cc041db9eecfe8 An old version
> 28da1ad8c1e468d8533eca68853f0d40 My current Mac OS X version
>
> And i also booted from Mac OS X, used the webcam and then rebooted
> Linux. it should have loaded the firmware corectly, but I didn't have
> any more success.
That won't work. You need to load a modified firmware, patched by ift-extract.
> ift-extract -a shows to me:
>
> ** Message: Found Mac OS X.4 intel driver
> ** Message: Firmware extracted successfully in /lib/firmware/isight.fw
> ** Message: Apply patch 0 : Fix video control interface descriptor
> ** Message: Apply patch 1 : Fix video streaming interface descriptor
> ** Message: Apply patch 2 : Fix video streaming device qualifier
> ** Message: Firmware patched successfully
>
> and
>
> ** Message: Found Mac OS X.5.1 driver
> ** Message: Firmware extracted successfully in /lib/firmware/isight.fw
> ** Message: Apply patch 0 : Fix video control interface descriptor
> ** Message: Apply patch 1 : Fix video streaming interface descriptor
> ** Message: Apply patch 2 : Fix video streaming device qualifier
> ** Message: Firmware patched successfully
>
> So, do you think the firmware is correctly loaded or not?
I don't know. You should contact the ift-extract author for help.
> In the meantime, I was looking at the driver source code (mainly
> ucv_driver.c), and I just discovered that the iSight webcam was referred
> as:
>
> /* Apple Built-In iSight */
> { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
>
> | USB_DEVICE_ID_MATCH_INT_INFO,
>
> .idVendor = 0x05ac,
> .idProduct = 0x8501,
> .bInterfaceClass = USB_CLASS_VIDEO,
> .bInterfaceSubClass = 1,
> .bInterfaceProtocol = 0,
> .driver_info = UVC_QUIRK_PROBE_MINMAX
>
> | UVC_QUIRK_BUILTIN_ISIGHT },
>
> And that my bInterfaceSubClass was 2 instead of 1. Changing that in the
> driver doesn't seems to help. When I load the driver (trace=255), I
> don't get any probe message.
bInterfaceSubClass shouldn't be changed. 1 is the right value. As explained
above, the first two interfaces look wrong.
> I think i'll have to find some documentation about the USB interface in
> the Linux kernel.
>
> I'd be glad if someone can find a solution to that issue.
I don't own any Mac so I can't really help you on this one. You should ocntact
the ift-extract author.
Best regards,
Laurent Pinchart
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
