Il 10/02/2011 02:59, Greg KH ha scritto:
On Thu, Feb 10, 2011 at 12:13:18AM +0000, mark205@xxxxxxxx wrote:
Hi there,
I have a problem. I'm trying to use the Microsoft Kinect with old
processors and also with small devices such as mobile phones that run
linux.
The openkinect driver uses the libusb library in order to get the data
from the Kinect. I'm interested at the depth/rgb video data (even only
one image). The camera has two high-bandwidth isochrnonous endpoints,
each of which does two 960-byte packets per microframe
The main problem is that, during the initialization phase I get the
errno 28: not enough free bandwidth available to schedule the
isochronous packets of the transfer.
The output of lsusb -v is this:
http://pastebin.com/b4r2aSk4
There is this comment on the MUSB host controller driver:
/* Bits 11& 12 of wMaxPacketSize encode high bandwidth multiplier.
* Some musb cores don't support high bandwidth ISO transfers; and
* we don't (yet!) support high bandwidth interrupt transfers.
*/
Do you know if is it possible to modify maybe the openkinect driver in
order to get at least one depth image.
It's not really a "driver" so much as just a userspace program using
libusb, right? Perhaps a "real" kernel driver should be written for the
device that exports the data properly to userspace through the video
apis instead?
Using musb for isoc endpoints that require lots of bandwidth on
low-speed processors might just not be possible, you have to take into
consideration your harware capabilities first.
good luck,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Ah, I was told that the kinect was used also on a router and this one
probably has a CPU slower than mine. So, the problem maybe is just the
musb.
Maybe changing that it will be possible to solve the problem...
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
