From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
linux-media@vger.kernel.org, srinivasa.deevi@conexant.com,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: cx231xx: DMA problem on ARM
Date: Mon, 26 Sep 2011 21:59:54 +0200 [thread overview]
Message-ID: <20110926215954.5ab059e4@skate> (raw)
In-Reply-To: <201109262102.49056.laurent.pinchart@ideasonboard.com>
Hello Laurent,
Le Mon, 26 Sep 2011 21:02:48 +0200,
Laurent Pinchart <laurent.pinchart@ideasonboard.com> a écrit :
> Are you using the MMAP or USERPTR capture method ? If using MMAP, can
> you try (as a test only) to unmap the buffer before queueing it and
> to remap it after dequeuing it ?
So far, we have used VLC, Cheese, or a simple OpenCV based application
to test the V4L2 device on our ARM platform, and I have no idea which
capture method those are using. Is there a very simple V4L test
application that we could use to hack the buffer unmap/remap trick
you're suggesting as a test ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-26 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 11:56 cx231xx: DMA problem on ARM Thomas Petazzoni
2011-09-21 12:04 ` Devin Heitmueller
2011-09-21 19:17 ` Thomas Petazzoni
2011-09-22 14:45 ` Thomas Petazzoni
2011-09-22 15:09 ` Devin Heitmueller
2011-09-22 15:29 ` Thomas Petazzoni
2011-09-23 12:04 ` Thomas Petazzoni
2011-09-23 12:26 ` Sri Deevi
2011-09-24 18:04 ` Thomas Petazzoni
2011-09-24 2:15 ` Mauro Carvalho Chehab
2011-09-26 8:13 ` Thomas Petazzoni
2011-09-26 17:32 ` Mauro Carvalho Chehab
2011-09-26 19:02 ` Laurent Pinchart
2011-09-26 19:59 ` Thomas Petazzoni [this message]
2011-09-26 20:03 ` Mauro Carvalho Chehab
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=20110926215954.5ab059e4@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=dheitmueller@kernellabs.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mchehab@redhat.com \
--cc=srinivasa.deevi@conexant.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.