Hi,
On Tuesday 22 December 2009 04:32:27 Yanbin Yue wrote:
> And my UVC device id is 0c45 : 62c0. When I search this code in the UVC
> dirver source, I can't find any item. Whether this device information need
> I add to the source code?
You don't need to add it. The uvcvideo driver matches aga
Hi,
On Tuesday 22 December 2009 03:43:05 Yanbin Yue wrote:
> The device is is a WIFI USB 2.0 device, it use the same USB slot, so I
> think the USB controller could work fine now. The error message as fllowing
>
>
> usb 1-1.4: device descriptor read/64, error 2
> usb 1-1.4: new full speed U
And my UVC device id is 0c45 : 62c0. When I search this code in the UVC
dirver source, I can't find any item. Whether this device information need
I add to the source code?
2009/12/22 Yanbin Yue
> I have used the external hub now, and the hub use external power. The error
> still in the same.
I have used the external hub now, and the hub use external power. The error
still in the same.
2009/12/19 Laurent Pinchart
> On Saturday 19 December 2009 06:40:40 Brian Pin wrote:
> > In this case I think you can't blame UVC, because it is shown your USB
> host
> > controller can not get descrip
The device is is a WIFI USB 2.0 device, it use the same USB slot, so I
think the USB controller could work fine now. The error message as fllowing
:
usb 1-1.4: device descriptor read/64, error 2
usb 1-1.4: new full speed USB device using musb_hdrc and address 5
usb 1-1.4: device descriptor re
In my previous reply, I saw the error is not related to UVC driver.
Also you have tested another USB device (is it an UVC device? you have to be
specific)
If this device you tested is UVC device, then your UVC driver is working
fine.
2009/12/21 Yanbin Yue
> HI,
>
> I have tested another US
On Saturday 19 December 2009 06:40:40 Brian Pin wrote:
> In this case I think you can't blame UVC, because it is shown your USB host
> controller can not get descriptor successfully, let alone to let UVC driver
> bind the device. So I think you should first check the device. See if its
> working an
In this case I think you can't blame UVC, because it is shown your USB host
controller can not get descriptor successfully, let alone to let UVC driver
bind the device. So I think you should first check the device. See if its
working anywhere. Or check the roothub of the port, maybe it has somethin
Hi,
After I configed USB_VIDEO_CLASS, when I plug the UVC Device to the
board, and "dmesg", there will be some error message as fllowing:
usb 1-1.4: device descriptor read/64, error 2
usb 1-1.4: new full speed USB device using musb_hdrc and address 5
usb 1-1.4: device descriptor read/64, error
Hi
2.6.28 already contains uvc host driver implementation.
You just need to find out 'USB_VIDEO_CLASS' during config. then you will
have the uvc driver support
On Fri, Dec 18, 2009 at 5:33 PM, 蔚艳斌 wrote:
> Hello everyone,
>
> My uvc devic ID is 0c45:62c0 . I can use it in my VM which o
Hello everyone,
My uvc devic ID is 0c45:62c0 . I can use it in my VM which os is
ubuntu 8.04. We want to use it in the OMAP3530-MINI board.
I don't know how complier the UVC source in my VM and then it can be used in
the OMAP3530-MINI. By the way, the kernel version is 2.6.24-26-generic in
11 matches
Mail list logo
