From: Oliver Collyer <ovcollyer@mac.com>
To: linux-media@vger.kernel.org
Cc: Andrey Utkin <andrey_utkin@fastmail.com>,
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 10:37:08 +0300 [thread overview]
Message-ID: <71006CF0-B710-435A-B5A5-C0D0D20DE34F@mac.com> (raw)
In-Reply-To: <20160906122823.toxscjyxomrh2col@zver>
> I am curious to tinker with this, just not sure about free time for it.
> Please go through the following instruction, and then we'll see if ssh
> is going to help to debug this.
>
> Also I think it is worth to CC actual manufacturers. There are addresses
> for technical support of both devices in public on maker websites.
> Please CC them when replying with new logs, to let them catch up.
>
Ok, so I’ve provided all these logs requested by Andrey in an earlier message but I’m unsubscribing from this list now.
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.
I’ve already documented another workaround ("modprobe -r uvcvideo && modprobe uvcvideo” before starting any capture) so really it’s up to the people developing these devices and/or the v4l2 driver/sub-system as to whether this gets sorted. Nobody from Magewell even bothered replying and I’m not going to chase that up as I’ve better things to do!
I am however, perfectly happy for anyone to contact me off list/copy me into any further discussion and I’m happy to provide ssh access to a machine that shows the problem for debugging if that would help.
- Oliver
next prev parent reply other threads:[~2016-09-10 7:37 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 [this message]
2016-09-10 10:14 ` Andrey Utkin
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=71006CF0-B710-435A-B5A5-C0D0D20DE34F@mac.com \
--to=ovcollyer@mac.com \
--cc=andrey_utkin@fastmail.com \
--cc=james.liu@magewell.net \
--cc=linux-media@vger.kernel.org \
--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