Linux Media Controller development
 help / color / mirror / Atom feed
From: Andrey Utkin <andrey_utkin@fastmail.com>
To: Oliver Collyer <ovcollyer@mac.com>
Cc: linux-media@vger.kernel.org,
	Support INOGENI <support@inogeni.com>,
	james.liu@magewell.net
Subject: Re: uvcvideo error on second capture from USB device, leading to V4L2_BUF_FLAG_ERROR
Date: Sat, 10 Sep 2016 13:14:40 +0300	[thread overview]
Message-ID: <20160910101440.nlb4sp43u36yj4ql@zver> (raw)
In-Reply-To: <71006CF0-B710-435A-B5A5-C0D0D20DE34F@mac.com>

On Sat, Sep 10, 2016 at 10:37:08AM +0300, Oliver Collyer wrote:
> Ok, so I’ve provided all these logs requested by Andrey in an earlier
> message but I’m unsubscribing from this list now.

Fine. You'll be able to post here, as well as receive replies for this
thread, without subscription.

> I have written a patch for FFmpeg that deals with the problem for both
> devices so it’s not really an issue for me anymore, but I’m not sure
> if the patch will get accepted in their master git as it’s a little
> messy.

Please post this patch here!

  reply	other threads:[~2016-09-10 10:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03  9:24 uvcvideo error on second capture from USB device, leading to V4L2_BUF_FLAG_ERROR Oliver Collyer
2016-09-04 19:25 ` Andrey Utkin
2016-09-04 19:55   ` Oliver Collyer
2016-09-05 19:43   ` Oliver Collyer
2016-09-05 20:19     ` Andrey Utkin
2016-09-05 20:32       ` Oliver Collyer
2016-09-06 10:51       ` Oliver Collyer
2016-09-06 12:28         ` Andrey Utkin
2016-09-06 17:26           ` Oliver Collyer
2016-09-10  7:37           ` Oliver Collyer
2016-09-10 10:14             ` Andrey Utkin [this message]
2016-09-10 10:21               ` Oliver Collyer
2016-09-10 10:58                 ` Andrey Utkin
2016-09-10 11:11                   ` Oliver Collyer

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=20160910101440.nlb4sp43u36yj4ql@zver \
    --to=andrey_utkin@fastmail.com \
    --cc=james.liu@magewell.net \
    --cc=linux-media@vger.kernel.org \
    --cc=ovcollyer@mac.com \
    --cc=support@inogeni.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