From: Hans de Goede <hdegoede@redhat.com>
To: alexander@xxor.de, linux-media@vger.kernel.org
Subject: Re: gspca second isoc endpoint / kinect depth
Date: Wed, 09 Apr 2014 11:05:58 +0200 [thread overview]
Message-ID: <53450D76.2010405@redhat.com> (raw)
In-Reply-To: <53443C5D.9000607@xxor.de>
Hi,
On 04/08/2014 08:13 PM, Alexander Sosna wrote:
> Hi,
>
> I took drivers/media/usb/gspca/kinect.c as skeleton to build a depth
> driver for the kinect camera.
>
> I needed to implement this feature because libfreenect performs so badly
> on the raspberry pi that you can't get a single frame.
>
> The kinecet has two isoc endpoints but gspca only uses the first.
> To get it running I made a dirty hack to drivers/media/usb/gspca/gspca.c
> I changed usb_host_endpoint *alt_xfer(...) so that it always returns the
> second endpoint, which is not really good for everyone.
>
>
> My driver is not ready for upstream now, it can not coexist with the
> current gspca_kinect so you have to decide if you want to load the video
> or the depth driver. Would be better to have one driver to do it all.
>
> But in the meantime I would like to ask for ideas about a more clean
> solution to get other isoc endpoints.
>
> There was already a little discussion about this when kinect.c was
> written by Antonio Ospite:
> http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/26194
>
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/26213
>
> Has something changed?
No.
> Is there a point against making multiple endpoints available?
No.
> Better solution?
Not that I know of.
Regards,
Hans
next prev parent reply other threads:[~2014-04-09 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 18:13 gspca second isoc endpoint / kinect depth Alexander Sosna
2014-04-09 9:05 ` Hans de Goede [this message]
2014-06-04 20:24 ` [RFC 0/2] gspca_kinect: add support for the depth stream Antonio Ospite
2014-06-04 20:24 ` [RFC 1/2] gspca: provide a mechanism to select a specific transfer endpoint Antonio Ospite
2014-06-19 14:27 ` Hans de Goede
2014-06-24 13:35 ` Antonio Ospite
2014-06-24 14:16 ` Hans de Goede
2014-06-04 20:24 ` [RFC 2/2] gspca_kinect: add support for the depth stream Antonio Ospite
2014-06-19 14:35 ` Hans de Goede
2014-06-25 8:00 ` Antonio Ospite
2014-06-25 9:27 ` [PATCH 0/2] gspca, " Antonio Ospite
2014-06-25 9:27 ` [PATCH 1/2] gspca: provide a mechanism to select a specific transfer endpoint Antonio Ospite
2014-06-25 9:27 ` [PATCH 2/2] gspca_kinect: add support for the depth stream Antonio Ospite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53450D76.2010405@redhat.com \
--to=hdegoede@redhat.com \
--cc=alexander@xxor.de \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.