From: Hans Verkuil <hverkuil@xs4all.nl>
To: Divneil Wadhawan <divneil@outlook.com>, Pawel Osciak <pawel@osciak.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: videobuf2-vmalloc suspect for corrupted data
Date: Mon, 07 Apr 2014 14:51:31 +0200 [thread overview]
Message-ID: <53429F53.7050005@xs4all.nl> (raw)
In-Reply-To: <BAY176-W91C143782DF21AB7ACEC8A9680@phx.gbl>
On 04/07/2014 01:20 PM, Divneil Wadhawan wrote:
> Hi Hans,
>> Two more questions:
>>
>> Which kernel version are you using?
> 3.4.58
That should be new enough, I see no important differences between 3.4
and 3.14 in this respect. But really, 3.4? That's over two years old!
If you have control over what kernel you use then I recommend you
upgrade.
>> Which capture driver are you using?
> It's a TSMUX driver, written locally.
I have not seen any reports of problems with vmalloc with arm in a long
time. I know the uvc driver uses vmalloc, and that's used frequently.
Question: if you use MEMORY_MMAP instead of USERPTR, does that work?
Have you tried to stream with v4l2-ctl? It's available here:
http://git.linuxtv.org/cgit.cgi/v4l-utils.git/. It's the reference
implementation of how to stream, so if that fails as well, then at
least its not your application.
Testing whether you see the same when capturing from a usb uvc webcam
(most webcams are uvc these days) would be useful as well. If it works
with a uvc webcam, but not with your driver, then I suspect the driver.
Regards,
Hans
next prev parent reply other threads:[~2014-04-07 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 9:56 videobuf2-vmalloc suspect for corrupted data Divneil Wadhawan
2014-04-07 10:27 ` Pawel Osciak
2014-04-07 10:49 ` Divneil Wadhawan
2014-04-07 10:57 ` Hans Verkuil
2014-04-07 11:20 ` Divneil Wadhawan
2014-04-07 11:46 ` Divneil Wadhawan
2014-04-07 12:51 ` Hans Verkuil [this message]
2014-04-08 9:55 ` Divneil Wadhawan
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=53429F53.7050005@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=divneil@outlook.com \
--cc=linux-media@vger.kernel.org \
--cc=pawel@osciak.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