[linux-uvc-devel] Support for Imaging Source cameras

[James Fidell]

There's a "fix" in the UVC driver allegedly to allow support for
"The Imaging Source USB CCD cameras". This picks up cameras
with the VID/PID 199e:8102. However, there appear to be quite a
number of IS USB CCD cameras that do not have this VID/PID (my
recent checks suggest that many are 199e:8101).

Imaging Source say these cameras (including the 199e:8101 models)
work under Linux with third party software and point to the Unicap
project website (http://unicap-imaging.org/index.htm). Any questions
addressed to IS about Linux support just get a referral to Unicap.
But it looks to me as if the Unicap project is unmaintained or
moribund. The support forums have been broken for some time and some
of the files referenced on the site appear to be missing.

So, can anyone shed any light on which Imaging Source USB CCD cameras
are supported and which aren't? I'm wondering if perhaps it's the case
that their "industrial" cameras are supported using the 199e:8102
VID/PID, but their "astronomy" cameras, based on the same hardware with
slightly different firmware, are not and have a different VID/PID
(199e:8101).

If there isn't actually any way to get these cameras to work on Linux
then I may suggest to IS that they remove from their website the link
saying that they are.

James

[Paulo Assis]

Hi,
are these models uvc compliant ?

please see:
http://www.ideasonboard.org/uvc/faq/

Regards,
Paulo

Post by James Fidell
There's a "fix" in the UVC driver allegedly to allow support for
"The Imaging Source USB CCD cameras". This picks up cameras
with the VID/PID 199e:8102. However, there appear to be quite a
number of IS USB CCD cameras that do not have this VID/PID (my
recent checks suggest that many are 199e:8101).
Imaging Source say these cameras (including the 199e:8101 models)
work under Linux with third party software and point to the Unicap
project website (http://unicap-imaging.org/index.htm). Any questions
addressed to IS about Linux support just get a referral to Unicap.
But it looks to me as if the Unicap project is unmaintained or
moribund. The support forums have been broken for some time and some
of the files referenced on the site appear to be missing.
So, can anyone shed any light on which Imaging Source USB CCD cameras
are supported and which aren't? I'm wondering if perhaps it's the case
that their "industrial" cameras are supported using the 199e:8102
VID/PID, but their "astronomy" cameras, based on the same hardware with
slightly different firmware, are not and have a different VID/PID
(199e:8101).
If there isn't actually any way to get these cameras to work on Linux
then I may suggest to IS that they remove from their website the link
saying that they are.
James
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Linux-uvc-devel mailing list
https://lists.sourceforge.net/lists/listinfo/linux-uvc-devel

[James Fidell]

Post by Paulo Assis
Hi,
are these models uvc compliant ?
http://www.ideasonboard.org/uvc/faq/

I'm trying to find out more details. It's possible that they're as
UVC-compliant as the supported models, which is to say "not strictly,
but close enough". I believe that like some of the Logitech cameras,
the supported models have a "vendor-specific" interface class rather
than video (that appears to be what the UVC driver in the 3.8 kernel
suggests anyhow), but otherwise are UVC-compliant.

Incidentally, this page:
http://www.ideasonboard.org/uvc/

claims my camera should work. 199e:8101 is listed as "device works"
in the "supported devices" table. And here's the output from dmesg:

[22074.228469] usb 1-1.3: new high-speed USB device number 9 using ehci-pci
[22074.323043] usb 1-1.3: New USB device found, idVendor=199e,
idProduct=8101

It is not recognised by the UVC driver however.

Initially it would just be useful to find anyone who knows anything
about the history of support for any of the Imaging Source USB CCD
cameras in the UVC driver so I can establish what models are expected
to be supported and what aren't.

James

[Paulo Assis]

Hi,

Post by James Fidell

Post by Paulo Assis
Hi,
are these models uvc compliant ?
http://www.ideasonboard.org/uvc/faq/

I'm trying to find out more details. It's possible that they're as
UVC-compliant as the supported models, which is to say "not strictly,
but close enough". I believe that like some of the Logitech cameras,
the supported models have a "vendor-specific" interface class rather
than video (that appears to be what the UVC driver in the 3.8 kernel
suggests anyhow), but otherwise are UVC-compliant.

What models exactly are these ?
As far as I know all logitech cameras are uvc compatible for a very
long time now.
Older models had some usb sync issues, that could cause a random
freeze on the video stream after a while, but still, they were uvc
compliant.

Post by James Fidell
http://www.ideasonboard.org/uvc/
claims my camera should work. 199e:8101 is listed as "device works"
[22074.228469] usb 1-1.3: new high-speed USB device number 9 using ehci-pci
[22074.323043] usb 1-1.3: New USB device found, idVendor=199e,
idProduct=8101
It is not recognised by the UVC driver however.

can you provide the output of: lsusb -d 199e:8101 -v

Regards,
Paulo

Post by James Fidell
Initially it would just be useful to find anyone who knows anything
about the history of support for any of the Imaging Source USB CCD
cameras in the UVC driver so I can establish what models are expected
to be supported and what aren't.
James

[James Fidell]

Post by Paulo Assis
What models exactly are these ?
As far as I know all logitech cameras are uvc compatible for a very
long time now.
Older models had some usb sync issues, that could cause a random
freeze on the video stream after a while, but still, they were uvc
compliant.

The ones listed in the source of uvc_driver.c with the comment

* The Logitech cameras listed below have their interface class set to
* VENDOR_SPEC because they don't announce themselves as UVC devices, even
* though they are compliant.

Ignore the Logitech issue though. My point was just that the Imaging
Source cameras with the 199e:8102 VID/PID appear to have a similar
issue.

Post by Paulo Assis
can you provide the output of: lsusb -d 199e:8101 -v

# lsusb -d 199e:8101 -v

Bus 001 Device 009: ID 199e:8101 The Imaging Source Europe GmbH DFx
21BU04 Camera
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x199e The Imaging Source Europe GmbH
idProduct 0x8101 DFx 21BU04 Camera
bcdDevice 1.00
iManufacturer 1 The Imaging Source Europe GmbH
iProduct 2 DFK 21AU618.AS
iSerial 3 11210205
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 366
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 255 Vendor Specific Class
bFunctionSubClass 3
bFunctionProtocol 0
iFunction 2 DFK 21AU618.AS
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 2 DFK 21AU618.AS
** UNRECOGNIZED: 0d 24 01 00 01 5d 00 10 27 00 00 01 01
** UNRECOGNIZED: 12 24 02 01 01 02 00 00 00 00 00 00 00 00 03 0a
00 00
** UNRECOGNIZED: 0b 24 05 02 06 00 00 02 ad 22 00
** UNRECOGNIZED: 09 24 03 03 01 01 00 02 00
** UNRECOGNIZED: 08 24 02 04 00 02 00 00
** UNRECOGNIZED: 07 24 04 05 01 02 00
** UNRECOGNIZED: 1b 24 06 06 0a ba 49 de 5c 0b 49 d5 8f 71 0b e4
0f 94 a6 7a 00 01 01 02 1f 43 00
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
** UNRECOGNIZED: 0e 24 01 01 45 00 81 00 03 00 00 00 01 00
** UNRECOGNIZED: 1b 24 04 01 01 59 55 59 32 00 00 10 00 80 00 00
aa 00 38 9b 71 10 01 10 09 86 00
** UNRECOGNIZED: 2a 24 05 01 00 80 02 e0 01 00 c2 01 00 00 a0 8c
00 00 60 09 00 15 16 05 00 04 15 16 05 00 2a 2c 0a 00 55 58 14 00 aa b0
28 00
** UNRECOGNIZED: 1c 24 10 02 01 59 38 30 30 00 00 10 00 80 00 00
aa 00 38 9b 71 08 01 10 09 86 00 00
** UNRECOGNIZED: 2e 24 11 01 00 80 02 e0 01 00 94 11 00 00 40 19
01 15 16 05 00 05 80 02 00 00 0a 8b 02 00 15 16 05 00 2a 2c 0a 00 55 58
14 00 aa b0 28 00
** UNRECOGNIZED: 1c 24 10 03 01 42 59 38 20 00 00 10 00 80 00 00
aa 00 38 9b 71 08 01 10 09 86 00 00
** UNRECOGNIZED: 2e 24 11 01 00 80 02 e0 01 00 94 11 00 00 40 19
01 15 16 05 00 05 80 02 00 00 0a 8b 02 00 15 16 05 00 2a 2c 0a 00 55 58
14 00 aa b0 28 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)


James

[A. C. Censi]

It seems that device is not listed in uvc_driver. This can solve the
problem?

https://bugs.mageia.org/show_bug.cgi?id=10219

Description of problem:
I have a ImagingSource DBK 21AU04 AS USb camera.
lsusb gives : Bus 007 Device 002: ID 199e:8101 The Imaging Source
Europe GmbH DFx 21BU04 Camera

it's driver is UVCDRIVER. But this one have only "8102" camera in
database. So I need to recompile every kernel with a little change.

The source : line 2361 of drivers/media/video/uvc/uvc_driver.c
/* The Imaging Source USB CCD cameras */
{ .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x199e,
.idProduct = 0x8102,
.bInterfaceClass = USB_CLASS_VENDOR_SPEC,
.bInterfaceSubClass = 1,
.bInterfaceProtocol = 0 },

The add juste after :
/* Imaging Source DFx 21BU04 */
{ .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x199e,
.idProduct = 0x8101,
.bInterfaceClass = USB_CLASS_VENDOR_SPEC,
.bInterfaceSubClass = 1,
.bInterfaceProtocol = 0,
.driver_info = UVC_QUIRK_PROBE_DEF
},


lspcidrake -v
before patching :
unknown : The Imaging Source Europe GmbH|DBx 21AU04.AS
<http://21au04.as/> (vendor:199e device:8101)

After patching :
uvcvideo : The Imaging Source Europe GmbH|DBx 21AU04.AS
<http://21au04.as/> (vendor:199e device:8101)


Another link:

http://linux-tipps.blogspot.com.br/2011/05/using-linux-driver-for-device-that-is.html

with this reference:

Erich Turnwald-Kurtz
<http://www.blogger.com/profile/09444433501900283754>September 24,
2012 at 1:54 PM
<http://linux-tipps.blogspot.com/2011/05/using-linux-driver-for-device-that-is.html?showComment=1348491285951#c5024695037971465863>

Ok, I have got a microscope camera, and lsusb tells me: ID 199e:8101
The Imaging Source Europe GmbH DFx 21BU04 Camera
I am using ubuntu 12.04 and no video device showed up when connecting
the camera. I tried the latest uvcvideo driver source. No success. But
when I did a root:
root$> echo "199e 8101" > /sys/bus/usb/drivers/uvcvideo/new_id
suddenly everything went fine :-)

Erich
etk(at)gluga(dot)de
==========


Best regards

ACC

Post by James Fidell
199e:8101 The Imaging Source Europe GmbH DFx

This can solve the problem?
https://bugs.mageia.org/show_bug.cgi?id=10219
I have a ImagingSource DBK 21AU04 AS USb camera.
lsusb gives : Bus 007 Device 002: ID 199e:8101 The Imaging Source Europe GmbH DFx 21BU04 Camera
it's driver is UVCDRIVER. But this one have only "8102" camera in database. So I need to recompile every kernel with a little change.
The source : line 2361 of drivers/media/video/uvc/uvc_driver.c
/* The Imaging Source USB CCD cameras */
{ .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x199e,
.idProduct = 0x8102,
.bInterfaceClass = USB_CLASS_VENDOR_SPEC,
.bInterfaceSubClass = 1,
.bInterfaceProtocol = 0 },
/* Imaging Source DFx 21BU04 */
{ .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x199e,
.idProduct = 0x8101,
.bInterfaceClass = USB_CLASS_VENDOR_SPEC,
.bInterfaceSubClass = 1,
.bInterfaceProtocol = 0,
.driver_info = UVC_QUIRK_PROBE_DEF
},
lspcidrake -v
unknown : The Imaging Source Europe GmbH|DBx 21AU04.AS (vendor:199e device:8101)
uvcvideo : The Imaging Source Europe GmbH|DBx 21AU04.AS (vendor:199e device:8101)
--
A. C. Censi
accensi [em] gmail [ponto] com
accensi [em] montreal [ponto] com [ponto] br

[James Fidell]

Post by A. C. Censi
It seems that device is not listed in uvc_driver. This can solve the
problem?
https://bugs.mageia.org/show_bug.cgi?id=10219

It doesn't appear to be a complete fix, though it may be a necessary
part of a fix should one be possible. The problem at the moment is
that I can't find anyone who knows the entire story.

James

[Paulo Assis]

Hi,

Post by James Fidell

Post by Paulo Assis
What models exactly are these ?
As far as I know all logitech cameras are uvc compatible for a very
long time now.
Older models had some usb sync issues, that could cause a random
freeze on the video stream after a while, but still, they were uvc
compliant.

The ones listed in the source of uvc_driver.c with the comment
* The Logitech cameras listed below have their interface class set to
* VENDOR_SPEC because they don't announce themselves as UVC devices, even
* though they are compliant.
Ignore the Logitech issue though. My point was just that the Imaging
Source cameras with the 199e:8102 VID/PID appear to have a similar
issue.

Post by Paulo Assis
can you provide the output of: lsusb -d 199e:8101 -v

# lsusb -d 199e:8101 -v
Bus 001 Device 009: ID 199e:8101 The Imaging Source Europe GmbH DFx 21BU04
Camera
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x199e The Imaging Source Europe GmbH
idProduct 0x8101 DFx 21BU04 Camera
bcdDevice 1.00
iManufacturer 1 The Imaging Source Europe GmbH
iProduct 2 DFK 21AU618.AS
iSerial 3 11210205
bNumConfigurations 1
bLength 9
bDescriptorType 2
wTotalLength 366
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 255 Vendor Specific Class
bFunctionSubClass 3
bFunctionProtocol 0
iFunction 2 DFK 21AU618.AS
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 2 DFK 21AU618.AS
** UNRECOGNIZED: 0d 24 01 00 01 5d 00 10 27 00 00 01 01
** UNRECOGNIZED: 12 24 02 01 01 02 00 00 00 00 00 00 00 00 03 0a 00
00
** UNRECOGNIZED: 0b 24 05 02 06 00 00 02 ad 22 00
** UNRECOGNIZED: 09 24 03 03 01 01 00 02 00
** UNRECOGNIZED: 08 24 02 04 00 02 00 00
** UNRECOGNIZED: 07 24 04 05 01 02 00
** UNRECOGNIZED: 1b 24 06 06 0a ba 49 de 5c 0b 49 d5 8f 71 0b e4 0f
94 a6 7a 00 01 01 02 1f 43 00
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
** UNRECOGNIZED: 0e 24 01 01 45 00 81 00 03 00 00 00 01 00
** UNRECOGNIZED: 1b 24 04 01 01 59 55 59 32 00 00 10 00 80 00 00 aa
00 38 9b 71 10 01 10 09 86 00
** UNRECOGNIZED: 2a 24 05 01 00 80 02 e0 01 00 c2 01 00 00 a0 8c 00
00 60 09 00 15 16 05 00 04 15 16 05 00 2a 2c 0a 00 55 58 14 00 aa b0 28 00
** UNRECOGNIZED: 1c 24 10 02 01 59 38 30 30 00 00 10 00 80 00 00 aa
00 38 9b 71 08 01 10 09 86 00 00
** UNRECOGNIZED: 2e 24 11 01 00 80 02 e0 01 00 94 11 00 00 40 19 01
15 16 05 00 05 80 02 00 00 0a 8b 02 00 15 16 05 00 2a 2c 0a 00 55 58 14 00
aa b0 28 00
** UNRECOGNIZED: 1c 24 10 03 01 42 59 38 20 00 00 10 00 80 00 00 aa
00 38 9b 71 08 01 10 09 86 00 00
** UNRECOGNIZED: 2e 24 11 01 00 80 02 e0 01 00 94 11 00 00 40 19 01
15 16 05 00 05 80 02 00 00 0a 8b 02 00 15 16 05 00 2a 2c 0a 00 55 58 14 00
aa b0 28 00
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

This camera uses a vendor specific protocol and it's not uvc compliant.
If you read http://unicap-imaging.org/tis_devices_en.htm there is no
claim that the cameras are uvc compliant, just that they use a similar
enought protocol. Unicap uses a custom usbdevfs driver, but they
provide a patch to enable some support for the cameras in the uvc
driver, although...
"This patch will not go into the mainlaine kernel because of the
ugliness of required hacks"

So the truth is that the cameras don't seem to be supported at all by
the kernel. I guess the only way to be sure if they work or not is to
patch the driver (although I doubt if the provided patch still applies
cleanly) and test it.

There are some old threads on the subject:
http://sourceforge.net/mailarchive/forum.php?thread_name=CAPueXH5Nerh6rbzFgL7KuvMVdOh-Nv1chTp_bHRF4QZ_ueqftw%40mail.gmail.com&forum_name=linux-uvc-devel

I guess you need at least to change your camera PID in the patch.


Regards,
Paulo

Post by James Fidell
James

[James Fidell]

Post by Paulo Assis
This camera uses a vendor specific protocol and it's not uvc compliant.
If you read http://unicap-imaging.org/tis_devices_en.htm there is no
claim that the cameras are uvc compliant, just that they use a similar
enought protocol.

Well, the page does say:

Information on Specific Devices

The Imaging Source USB CCD Cameras ( AU/BU Series )

These cameras are UVC compliant but they have a vendor specific
interface class specified in the USB descriptors. Due to this, the
uvcvideo driver does not detect these cameras.

Personally I'd interpret that as a claim that it's UVC compliant, but
I guess that depends exactly what you mean by "compliant" :)

If it truly isn't UVC compliant then I guess the entry for 199e:8101
needs changing on this page

http://www.ideasonboard.org/uvc/

to at least document the fact that the driver may well not support all,
or perhaps even any, such devices.

James

[Paulo Assis]

Hi,

Post by James Fidell

Post by Paulo Assis
This camera uses a vendor specific protocol and it's not uvc compliant.
If you read http://unicap-imaging.org/tis_devices_en.htm there is no
claim that the cameras are uvc compliant, just that they use a similar
enought protocol.

Information on Specific Devices
The Imaging Source USB CCD Cameras ( AU/BU Series )
These cameras are UVC compliant but they have a vendor specific
interface class specified in the USB descriptors. Due to this, the
uvcvideo driver does not detect these cameras.
Personally I'd interpret that as a claim that it's UVC compliant, but
I guess that depends exactly what you mean by "compliant" :)
If it truly isn't UVC compliant then I guess the entry for 199e:8101
needs changing on this page
http://www.ideasonboard.org/uvc/
to at least document the fact that the driver may well not support all,
or perhaps even any, such devices.

You are probably right, but if it's there, then someone confirmed that
a device with that exact VID/PID was working at some point with the
uvc driver.
I'm not sure if different revisions of that device/firmware would
still be labeled with the same PID, but I guess that can happen. That
at least would explain why a certain device works and another one
don't.
In any case if the device is actually UVC compliant, then simply
mapping it's VID:PID in the driver should be enough to make it work.

Regards,
Paulo

Post by James Fidell
James

[James Fidell]

Post by Paulo Assis
You are probably right, but if it's there, then someone confirmed that
a device with that exact VID/PID was working at some point with the
uvc driver.
I'm not sure if different revisions of that device/firmware would
still be labeled with the same PID, but I guess that can happen. That
at least would explain why a certain device works and another one
don't.
In any case if the device is actually UVC compliant, then simply
mapping it's VID:PID in the driver should be enough to make it work.

This is really why it would be useful to contact someone who knows the
history. I think there's more going on here than is immediately
obvious. For example, all of the cameras on this webpage:

http://www.firstlightoptics.com/imaging-source-cameras.html

are supported according to the ideasonboard.org supported devices list
(they all have VID/PID 199e:8101), but I don't believe any of them will
actually work.

It is possible that there was another firmware release for most of these
cameras to make them fully UVC-compliant, but I haven't got to the
bottom of that yet. I would be tempted to take the view that "fully"
compliant means no deviation from the standard at all, so claiming to
have a vendor-specific interface type wouldn't count. On the other
hand, perhaps the alternative firmware release changed the PID so it
would work. And if different firmware is required to achieve full UVC
compliance, perhaps the default firmware is "close enough" to be able
to get images out of the camera given the right configuration.

It's all very confusing :(

However, I have a written capture application that works for V4L2
devices and some non-V4L2 USB cameras, so I shall push on making it work
where I can and see how far I can get.

Thanks for your help so far.

James

[James Fidell]

Post by Paulo Assis
This camera uses a vendor specific protocol and it's not uvc compliant.
If you read http://unicap-imaging.org/tis_devices_en.htm there is no
claim that the cameras are uvc compliant, just that they use a similar
enought protocol. Unicap uses a custom usbdevfs driver, but they
provide a patch to enable some support for the cameras in the uvc
driver, although...
"This patch will not go into the mainlaine kernel because of the
ugliness of required hacks"

It looks like the CMOS-sensor cameras are supported using a usbdevfs
and have the patch that cannot go back into the kernel.

The CCD-sensor cameras have a patch that has gone into the kernel
already. It's the CCD cameras that I am interested in, and (one of)
the CCD cameras that I posted the lsusb output for.

James

[Daniel Mosquera]

There is a firmware that have to be loaded in order to make the camera partially uvc compliant. After loading it the camera returns the Bayer pattern instead a proper image format.
In 8 hours i'll post the link to the github pro

[Daniel Mosquera]

I've remembered the name of the project some minutes ago. Here it goes the link.

http://code.google.com/p/tiscamera/wiki/GettingStartedCMOSUVC

Post by Daniel Mosquera
There is a firmware that have to be loaded in order to make the camera partially uvc compliant. After loading it the camera returns the Bayer pattern instead a proper image format.
In 8 hours i'll post the link to the github project to the firmware. I don't have it in my phone

[James Fidell]

Post by Daniel Mosquera
I've remembered the name of the project some minutes ago. Here it goes the link.
http://code.google.com/p/tiscamera/wiki/GettingStartedCMOSUVC

Ahhh, that one is also apparently only for the CMOS-based cameras, not
the CCD ones.

James