Re: [Linux-uvc-devel] Unsupported webcam: STMicroelectronics Imaging Division (VLSI Vision)

2009-02-24 Thread Laurent Pinchart
On Monday 23 February 2009 06:18:00 Juho Vähä-Herttua wrote:
 Nathan Baker wrote:
  Hm, well, if it's not a uvc device, do you have any idea where I should
  look to get the driver?

 I'll start with a small rant. If you're coming from this thread:
 http://www.linuxquestions.org/questions/linux-hardware-18/cant-get-usb-webc
am-to-work-706318/, I think someone could mention to BigVig about the FAQ
 http://linux-uvc.berlios.de/faq/ and especially the first question. It's
 not very useful to post the lsusb dump if the device is not UVC device
 to begin with, so pointing new users here is a bit misinformation, but
 then again the lsusb wasn't very correct either.

I'd appreciate if someone with a linuxquestions.org account could do that. I 
already have too many mailing lists to monitor, I don't feel like registering 
to yet another forum (I guess we really need OpenID).

Best regards,

Laurent Pinchart

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


Re: [Linux-uvc-devel] Unsupported webcam: STMicroelectronics Imaging Division (VLSI Vision)

2009-02-22 Thread ADFH
Hi,

 [nat...@ebisu ~] sudo lsusb -v
 Bus 006 Device 008: ID 0553:0a02 STMicroelectronics Imaging Division
 (VLSI Vision)

   iManufacturer   1 5 button optical mouse with scroll wheel
   iProduct3 5 button optical mouse with scroll wheel
...
   bInterfaceClass 3 Human Interface Device
   bInterfaceSubClass  1 Boot Interface Subclass
   bInterfaceProtocol  2 Mouse

This seems to be the USB details on your mouse, not your webcam..
When you plugged in your webcam, it showed ID 17a1:0118 (based upon
thread on messageboard link)..
This lsusb output above shows ID 0553:0a02 and talks about your mouse..

1. Plug the webcam in
2. Check dmesg output for the connected ID (Ie. 17a1:0118)
   Ie. $ dmesg | less
   ... jump to the bottom and look at the most recent USB connection messages
   for ID.. q to quit less..
3. Run lsusb -v and output to a text file
   Ie. $ sudo lsusb -v  /tmp/lsusb.txt
4. Search that text file (/tmp/lsusb.txt) for the ID you recorded earlier
5. Post everything from the line that says:
   Bus XXX Device XXX: ID : ..
   ... through to the end of the output, or the next Bus XXX Device XXX
   line, whichever comes first

The webcam must be plugged in when you're running lsusb..
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


Re: [Linux-uvc-devel] Unsupported webcam: STMicroelectronics Imaging Division (VLSI Vision)

2009-02-22 Thread Nathan Baker
Wow, sorry, I saw imaging and figured I had the right thing. My bad.

Here's the right one:

===
Bus 001 Device 015: ID 17a1:0118
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x17a1
  idProduct  0x0118
  bcdDevice1.00
  iManufacturer  64 TASCORP
  iProduct   77 USB2.0 WebCam
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   57
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xc0
  Self Powered
MaxPower   96mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 0 (Defined at Interface level)
  bInterfaceSubClass  0
  bInterfaceProtocol  0
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   1
  bInterfaceClass 0 (Defined at Interface level)
  bInterfaceSubClass  0
  bInterfaceProtocol  0
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   2
  bNumEndpoints   1
  bInterfaceClass 0 (Defined at Interface level)
  bInterfaceSubClass  0
  bInterfaceProtocol  0
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x03c0  1x 960 bytes
bInterval   1
Device Status: 0x
  (Bus Powered)
===

Again, sorry for the fail.

Thanks,
Nathan


ADFH wrote:
 Hi,

   
 [nat...@ebisu ~] sudo lsusb -v
 Bus 006 Device 008: ID 0553:0a02 STMicroelectronics Imaging Division
 (VLSI Vision)
 
 
   
   iManufacturer   1 5 button optical mouse with scroll wheel
   iProduct3 5 button optical mouse with scroll wheel
 
 ...
   
   bInterfaceClass 3 Human Interface Device
   bInterfaceSubClass  1 Boot Interface Subclass
   bInterfaceProtocol  2 Mouse
 

 This seems to be the USB details on your mouse, not your webcam..
 When you plugged in your webcam, it showed ID 17a1:0118 (based upon
 thread on messageboard link)..
 This lsusb output above shows ID 0553:0a02 and talks about your mouse..

 1. Plug the webcam in
 2. Check dmesg output for the connected ID (Ie. 17a1:0118)
Ie. $ dmesg | less
... jump to the bottom and look at the most recent USB connection messages
for ID.. q to quit less..
 3. Run lsusb -v and output to a text file
Ie. $ sudo lsusb -v  /tmp/lsusb.txt
 4. Search that text file (/tmp/lsusb.txt) for the ID you recorded earlier
 5. Post everything from the line that says:
Bus XXX Device XXX: ID : ..
... through to the end of the output, or the next Bus XXX Device XXX
line, whichever comes first

 The webcam must be plugged in when you're running lsusb..
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

   
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


Re: [Linux-uvc-devel] Unsupported webcam: STMicroelectronics Imaging Division (VLSI Vision)

2009-02-22 Thread ADFH
Hi Nathan,

 Here's the right one:

Looking at http://linux-uvc.berlios.de/faq/ it would appear that your
camera doesn't say that it's USB Video Class compatible.

Ie. My camera shows:

$ sudo lsusb -vd 0489:d00a | grep 14 Video
  bFunctionClass 14 Video
  bInterfaceClass14 Video
  bInterfaceClass14 Video

Yours doesn't have any Video class entries.

(Someone else feel free to chime in here if I've fluffed up my reading
of the doco)

Anthony
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


Re: [Linux-uvc-devel] Unsupported webcam: STMicroelectronics Imaging Division (VLSI Vision)

2009-02-22 Thread Nathan Baker
Hm, well, if it's not a uvc device, do you have any idea where I should
look to get the driver?

Thanks,
Nathan

ADFH wrote:
 Hi Nathan,

   
 Here's the right one:
 

 Looking at http://linux-uvc.berlios.de/faq/ it would appear that your
 camera doesn't say that it's USB Video Class compatible.

 Ie. My camera shows:

 $ sudo lsusb -vd 0489:d00a | grep 14 Video
   bFunctionClass 14 Video
   bInterfaceClass14 Video
   bInterfaceClass14 Video

 Yours doesn't have any Video class entries.

 (Someone else feel free to chime in here if I've fluffed up my reading
 of the doco)

 Anthony

   
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


Re: [Linux-uvc-devel] Unsupported webcam: STMicroelectronics Imaging Division (VLSI Vision)

2009-02-22 Thread ADFH
Hi,

 Hm, well, if it's not a uvc device, do you have any idea where I
 should look to get the driver?

Unfortunately it looks like it's not supported by the GSPCA driver
either ... http://mxhaard.free.fr/spca5xx.html

You could try googling for the device ID - on cursory examination it
looks like there might be some other people trying as well.

Another thing to try is looking through the windows drivers for
manufacturer info and seeing if there's any google hits against the
listed manufacturer in the drivers ... +linux +webcam etc. etc.

Anthony
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel