| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | debris` has quit IRC (Ping timeout: 276 seconds) | [01:41] |
| .................................................................................................................................................. (idle for 12h9mn) | ||
| crazy_imp | heyho
I got a leap motion, which should be uvc compatible (at least uvc didn't complain about it and the device descriptors should be fine - http://pastebin.com/R60j90ji (dmesg dump)) - but I got no video device any hints to get it working as such? :) | [13:50] |
| *** | d00gster has quit IRC (Remote host closed the connection) | [14:01] |
| crazy_imp | ok, added the right vid:pid into my modules.alias, now it shows up, but not really useable :D | [14:10] |
| .................................................. (idle for 4h9mn) | ||
| pinchartl | crazy_imp: adding the vid:pid shouldn't be needed if the device is uvc-compliant
how is it not really useable ? | [18:19] |
| ................................. (idle for 2h41mn) | ||
| crazy_imp | pinchartl: guvcview lists it, including a bunch of controls, but it doesn't give you any data | [21:00] |
| ..... (idle for 21mn) | ||
| pinchartl | crazy_imp: any message in the kernel log when you try to stream video data ?
could you try to capture frames with the command line yavta test application ? | [21:21] |
| crazy_imp | pinchartl: any parameters I should use with yavtv? | [21:27] |
| pinchartl | -s for the resolution, -f for the format, -c10 to capture 10 frames, -F to save them to files
-h to get help :-) | [21:29] |
| crazy_imp | pinchartl: http://pastebin.com/DWXYkc7e
someone else already pointed out, that it needs some special transfers before you can use it. guess I'll try his module first | [21:40] |
| ......... (idle for 42mn) | ||
| pinchartl | crazy_imp: special tranfers ? do you have more information about that ? | [22:23] |
| crazy_imp | pinchartl: http://www.spinics.net/lists/linux-usb/msg131346.html also the original leapd (daemon to interface the hardware) does quite a bunch stuff with libusb and got a thread named "UVCStateMachine". about 8k calls into libusb before it decides that the firmware on the device is up to date and so on
the mentioned kernel module should be https://github.com/SMFloris/kernelmotion | [22:28] |
| pinchartl | it would be nice to get the code merged in the uvcvideo driver if possible
and the vendor shouldn't be allowed to claim uvc compliance, the device is clearly not compliant | [22:31] |
| crazy_imp | like setting up a compilant looking device descriptor? | [22:36] |
| pinchartl | yes, they should have used a vendor-specific descriptor | [22:39] |
| crazy_imp | would be nicer if it would be compliant or they opensourced their code | [22:41] |
| pinchartl | it would be much nicer if it was compliant, yes
as always | [22:44] |
| crazy_imp | does uvc handle stereo cameras? | [22:45] |
| pinchartl | it handles them as two separate cameras
well, it can handle them as a single camera but most devices don't implement that it's really up to the device, the specification and the driver can handle cameras that produce two video streams | [22:48] |
| crazy_imp | the leap should give you alternating one byte from the left and right camera
(at least you cannot run out of sync this way ;) | [22:50] |
| pinchartl | that's just awful :-)
it could still be supported in V4L2 userspace would need to handle that custom format though | [22:53] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |