From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ironport2-out.teksavvy.com ([206.248.154.181]:28611 "EHLO ironport2-out.teksavvy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754742AbbJAASb (ORCPT ); Wed, 30 Sep 2015 20:18:31 -0400 Subject: Re: uvc-1.5 To: Mauro Carvalho Chehab References: <560B196A.2020704@lockie.ca> <20150930201300.66ab1478@recife.lan> Cc: linux-media@vger.kernel.org From: James Message-ID: <560C7BD0.7070204@lockie.ca> Date: Wed, 30 Sep 2015 20:18:24 -0400 MIME-Version: 1.0 In-Reply-To: <20150930201300.66ab1478@recife.lan> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: On 09/30/15 19:13, Mauro Carvalho Chehab wrote: > Em Tue, 29 Sep 2015 19:06:18 -0400 > James 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).