Hi Mildred, On Saturday 21 June 2008, Mildred wrote: > Hi, > > I'm writing here since it seems that now, iSight code seems to be part > of UVC. And I'm having a problem with it (/dev/video0 not created). > > So I built the uvcvideo driver (trunk r217) and built iSight Firmware > Tools 1.2 (and restarted HAL). When I load the driver, dmesg only tells > me: > > usbcore: registered new interface driver uvcvideo > > Nothing else. > if I modprobe uvcvideo race=255, I get: > [snip] > > The problem is that no device /dev/video0 is created, so gstreamer > fails with a message like > > Error running pipeline 'Video for Linux 2 (v4l2)': Cannot identify device > '/dev/video0'. [v4l2_calls.c(429): gst_v4l2_open (): /pipeline0/v4l2src3: > system error: No such file or directory] > > > I don't think that's a problem regarding the firmware loading since I > used an old binary called 'extract' that worked back in time. It tells > me that the iSight firmware is loaded: > > Apple iSight with firmware already loaded found > Apple iSight with firmware already loaded found > > > There is an output of lsusb: > > $ sudo lsusb -d 05ac:8501 -v > > Bus 002 Device 003: ID 05ac:8501 Apple Computer, Inc. Built-in iSight > [Micron] Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize0 64 > idVendor 0x05ac Apple Computer, Inc. > idProduct 0x8501 Built-in iSight [Micron] > bcdDevice 1.84 > iManufacturer 1 Micron > iProduct 2 Built-in iSight > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 267 > bNumInterfaces 2 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 100mA > ** UNRECOGNIZED: 08 24 00 02 ff ff ff 00 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol [snip]
bInterfaceClass should be set to '14 Video'. This means your firmware hasn't been patched. > 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. Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
