From: James <bjlockie@lockie.ca>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org
Subject: Re: uvc-1.5
Date: Wed, 30 Sep 2015 20:18:24 -0400 [thread overview]
Message-ID: <560C7BD0.7070204@lockie.ca> (raw)
In-Reply-To: <20150930201300.66ab1478@recife.lan>
On 09/30/15 19:13, Mauro Carvalho Chehab wrote:
> Em Tue, 29 Sep 2015 19:06:18 -0400
> James <bjlockie@lockie.ca> escreveu:
>
>> When is the Linux kernel going to support uvc-1.5?
>> It was made a standard on June 6, 2012
> When someone writes patches adding support for it, together with the
> code that adds support to at least one device that uses UVC 1.5 ;)
>
> I dunno if anyone is working on that ATM.
>
> Regards,
> Mauro
Apparently there was a patch in 2013.
https://www.mail-archive.com/linux-media@vger.kernel.org/msg66199.html
If the patch is in the kernel, I don't think it works any more.
If the patch never made it into the kernel then I don't know why (my
guess is it has something to do with QP controls).
prev parent reply other threads:[~2015-10-01 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 23:06 uvc-1.5 James
2015-09-30 23:13 ` uvc-1.5 Mauro Carvalho Chehab
2015-10-01 0:18 ` James [this message]
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=560C7BD0.7070204@lockie.ca \
--to=bjlockie@lockie.ca \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).