Quoting sjb <[EMAIL PROTECTED]>: > As I load the modules, it says .. > > Sep 1 10:47:50 vaio kernel: Linux video capture interface: v1.00 > Sep 1 10:48:39 vaio kernel: usb.c: registered new driver nw802 > Sep 1 10:48:39 vaio kernel: nw802.c: Module loaded
Good. Almost good, that is...
> >cat /proc/bus/usb/devices (after you plug the camera in)
>
> T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
> P: Vendor=093a ProdID=0007 Rev= 1.00
================================= <-- SEE HERE
> S: Product=USB camera
[snipped]
But look at the driver source!!!
#define DIVIO_VENDORID 0x06A5
#define NW802_PRODUCTID 0xD001
// Check Vendor & Product ID
if ( ( dev->descriptor.idVendor != DIVIO_VENDORID ) ||
( dev->descriptor.idProduct != NW802_PRODUCTID ) )
return NULL;
// Ok it's a supported cam ( at least seems to )
INFO( "Divio NW802 based webcam found !" );
As you can see, your camera has completely different Product and Vendor ID
- no surprise that the driver does not want to service it :-)
What you can do is this: hack the #defines above in the driver source (put
yours own there) and see if it helps. If not, contact the author of the
driver.
It is not uncommon for OEMs to play with IDs - the IP OEM uses their own
codes, then the manufacturer replaces them with their own... so it all
might very well work. Just change the IDs and recompile the driver, then
reload it and see what happens!
Dmitri
--
65. If I must have computer systems with publically available terminals,
the maps they display of my complex will have a room clearly marked
as the Main Control Room. That room will be the Execution Chamber.
The actual main control room will be marked as Sewage Overflow Containment.
("Evil Overlord" by Peter Anspach and John VanSickl)
msg04642/pgp00000.pgp
Description: PGP signature
