From: Oleksij Rempel <linux@rempel-privat.de>
To: Peter Ross <pross@xvid.org>, linux-uvc-devel@lists.sourceforge.net
Cc: linux-media@vger.kernel.org
Subject: Re: [linux-uvc-devel] [PATCHv2 0/2] uvcvideo: Support Logitech RGB Bayer formats
Date: Sun, 23 Feb 2014 12:39:17 +0100 [thread overview]
Message-ID: <5309DDE5.6040101@rempel-privat.de> (raw)
In-Reply-To: <cover.1393133476.git.pross@xvid.org>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
Am 23.02.2014 06:54, schrieb Peter Ross:
>
> PATCHv1 discussion: http://sourceforge.net/mailarchive/message.php?msg_id=31541036
> and http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/70192
>
> On Sun, Oct 20, 2013 at 11:54:10AM +0200, Oleksij Rempel wrote
> [..]
>>> Hello Peter, Laurent,
>>> Peter do have time to update this patches for latest kernel? Laurent
>>>
>>> would you accept them?
>
> Here are is updated pachset. They have been tested against uvcvideo-next
> today (3.14.0-rc) using FFmpeg's V4L2 grabber.
>
> Peter Ross (2):
> videodev2: add V4L2_PIX_FMT_Sxxxx10_1X10 formats
> uvcvideo: Support Logitech RGB Bayer formats
>
> drivers/media/usb/uvc/uvc_driver.c | 176 +++++++++++++++++++++++++++++++++++++
> drivers/media/usb/uvc/uvc_video.c | 48 ++++++++++
> drivers/media/usb/uvc/uvcvideo.h | 22 +++++
> include/uapi/linux/videodev2.h | 4 +
> 4 files changed, 250 insertions(+)
>
I have some problems to use this patch set with guvcview. Frame rate
info seems to be corrupt for bayer. There are only some random values.
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 278 bytes --]
prev parent reply other threads:[~2014-02-23 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 5:54 [PATCHv2 0/2] uvcvideo: Support Logitech RGB Bayer formats Peter Ross
2014-02-23 11:39 ` Oleksij Rempel [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=5309DDE5.6040101@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-uvc-devel@lists.sourceforge.net \
--cc=pross@xvid.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox