I have found out what the issue was. the kernel didnt have support for these and once i turned on, everything became ok.
thanks and regards -- anees On Wed, Jul 2, 2008 at 11:08 AM, aneeskA <[EMAIL PROTECTED]> wrote: > Hi Laurent, > > Thanks for that info. It was highly useful. Theres one more thing > regarding UVC driver. When i try to compile the driver the following symbols > are said to be undefined:- > > input_allocate_device() > > input_register_device() > > input_unregister_device() > > input_free_device() > > all are from the file -- uvc_status.c. Any idea why this is so ? although > this is reported as warning it prevents me from loading the module. Any help > is highly appreciated. > > thanks and regards > > -- anees > > > On Wed, Jul 2, 2008 at 1:33 AM, Laurent Pinchart < > [EMAIL PROTECTED]> wrote: > >> Hi Anees, >> >> On Tuesday 01 July 2008, aneeskA wrote: >> > Hi Laurent, >> > >> > from *http://linux-uvc.berlios.de/* i downloaded uvc driver using >> > "*svn checkout svn://svn.berlios.de/linux-uvc/linux-uvc/trunk*" . the >> > "Supported Devides" section lists Omnivision cams. but in the code i >> cant >> > find their Vendor id or product id in "*static struct usb_device_id >> > uvc_ids[] = {*" file :- uvc_driver.c line :- 1701. >> > >> > any idea why it is so ? >> >> Because UVC devices report UVC compatibility in the bInterfaceClass and >> bInterfaceSubClass fields. The VID:PID is only used for non-compliant >> devices >> that require special handling from the driver. >> >> Best regards, >> >> Laurent Pinchart >> > >
_______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
