Re: Kinect sensor and Linux kernel driver.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Are the Pan/Tilt/Zoom controls exposed ?

Given that the Kinect can move it actually makes a pretty cheap PTV
option for video conferences.

-JoelW

On 7 December 2010 10:50, Jason <openkinect@xxxxxxxxxxxxxx> wrote:
> On 12/06/2010 04:18 PM, Antonio Ospite wrote:
>> Now the hard part begins, here's a loose TODO-list:
>> Â - Discuss the "fragmentation problem":
>> Â Â Â* the webcam kernel driver and the libusb backend of libfreenect
>> Â Â Â Âare not going to conflict each other in practice, but code
>> Â Â Â Âduplication could be avoided to some degree; we could start
>> Â Â Â Âlisting the advantages and disadvantages of a v4l2 backend
>> Â Â Â Âopposed to a libusb backend for video data in libfreenct (don't
>> Â Â Â Âthink in terms of userspace/kernelspace for now).
>
> I've got a patchset in the works for this, just trying to view Y16 from
> userspace first...
>
>> Â Â Â* Would exposing the accelerometer as an input device make sense
>> Â Â Â Âtoo? The only reason for that is to use the data in already
>> Â Â Â Âexisting applications. And what about led and motor?
>
> embedded applications may find this helpful...
>
>> Â Â If we agree that the kernel driver approach is not too dangerous
>> Â Â for libfreenect's future, than we could start talking about
>> Â Â submitting code to mainline linux.
>
> always a good idea. ÂI'm pretty sure the motion project [1] could make
> use of a v4l device that spits out smoothed depth data...
>
>> Â - Check if gspca can handle two video nodes for the same USB device
>> Â Â in a single driver (Kinect sensor uses ep 0x81 for color data and
>> Â Â ep 0x82 for depth data).
>
> wip.
>
>> Â - Decide if we want two separate video nodes, or a
>> Â Â combined RGB-D data stream coming from a single video device node.
>> Â Â (I haven't even looked at the synchronization logic yet).
>
> There is a timestamp field with every frame passed on by the kinect, can
> that be passed up to v4l?
>
> Also, if we decide to stay with two video nodes, some udev magic could
> create:
>
> /dev/kinect/depth -> ../videoX
> /dev/kinect/camera -> ../videoY
> /dev/kinect/ir -> ../videoZ
> ...
>
> For consistent naming.
>
> thx,
>
> Jason.
>
> [1] http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux