From: Andy Walls <awalls@md.metrocast.net>
To: Hans Verkuil <hansverk@cisco.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sylwester Nawrocki <snjw23@gmail.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Kim HeungJun <riverful@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stanimir Varbanov <svarbanov@mm-sol.com>
Subject: Re: [RFC] snapshot mode, flash capabilities and control
Date: Mon, 28 Feb 2011 08:33:44 -0500 [thread overview]
Message-ID: <1298900024.2137.31.camel@morgan.silverblock.net> (raw)
In-Reply-To: <201102281217.12538.hansverk@cisco.com>
On Mon, 2011-02-28 at 12:17 +0100, Hans Verkuil wrote:
> On Monday, February 28, 2011 12:07:33 Laurent Pinchart wrote:
> > > So, do I understand it right, that currently there are drivers, that
> > > overwrite the last buffers while waiting for a new one, and ones, that
> > > stop capture for that time.
>
> Does anyone know which drivers stop capture if there are no buffers available?
> I'm not aware of any.
Not that it is a camera driver, but...
cx18 will stall the stream, due to the CX23418 engine being starved of
buffers for that stream, if the application doesn't read the buffers.
The reasoning for this behavior is that one large gap is better than a
series of small gaps, if the application has fallen behind.
The exceptional case is the cx18 MPEG Index stream, which will steal the
oldest buffers back in the call to cx18_stream_rotate_idx_mdls().
The CX23418 engine seems to gracefully handle being starved of buffers
for a stream for a period of time.
This driver does not use videobuf currently.
-Andy
next prev parent reply other threads:[~2011-02-28 13:33 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 12:18 [RFC] snapshot mode, flash capabilities and control Guennadi Liakhovetski
2011-02-24 12:40 ` Hans Verkuil
2011-02-24 16:07 ` Guennadi Liakhovetski
2011-02-24 17:57 ` Kim HeungJun
2011-02-25 10:05 ` Laurent Pinchart
2011-02-25 13:53 ` Sakari Ailus
2011-02-25 17:08 ` Guennadi Liakhovetski
2011-02-25 18:55 ` Sakari Ailus
2011-02-25 20:56 ` Guennadi Liakhovetski
2011-02-28 11:57 ` Guennadi Liakhovetski
2011-03-06 9:53 ` Sakari Ailus
2011-02-26 12:31 ` Hans Verkuil
2011-02-26 13:03 ` Guennadi Liakhovetski
2011-02-26 13:39 ` Sylwester Nawrocki
2011-02-26 13:56 ` Hans Verkuil
2011-02-26 15:42 ` Sylwester Nawrocki
2011-02-28 10:28 ` Laurent Pinchart
2011-02-28 10:40 ` Hans Verkuil
2011-02-28 10:47 ` Laurent Pinchart
2011-02-28 11:02 ` Guennadi Liakhovetski
2011-02-28 11:07 ` Laurent Pinchart
2011-02-28 11:17 ` Hans Verkuil
2011-02-28 11:19 ` Laurent Pinchart
2011-02-28 11:54 ` Guennadi Liakhovetski
2011-02-28 22:41 ` Guennadi Liakhovetski
2011-03-02 17:51 ` Guennadi Liakhovetski
2011-03-02 18:19 ` Hans Verkuil
2011-03-03 1:05 ` Andy Walls
2011-03-03 11:50 ` Laurent Pinchart
2011-03-03 13:56 ` Andy Walls
2011-03-03 14:04 ` Laurent Pinchart
2011-03-03 14:55 ` Andy Walls
2011-03-03 14:29 ` Sakari Ailus
2011-03-03 8:02 ` Guennadi Liakhovetski
2011-03-03 9:25 ` Hans Verkuil
2011-02-28 13:33 ` Andy Walls [this message]
2011-02-28 13:37 ` Andy Walls
2011-02-28 11:37 ` Guennadi Liakhovetski
2011-02-28 12:03 ` Sakari Ailus
2011-02-28 12:44 ` Guennadi Liakhovetski
2011-02-28 15:07 ` Sakari Ailus
2011-02-28 10:24 ` Laurent Pinchart
2011-02-25 16:58 ` Guennadi Liakhovetski
2011-02-25 18:49 ` Sakari Ailus
2011-02-25 20:33 ` Guennadi Liakhovetski
2011-02-27 21:00 ` Sakari Ailus
2011-02-28 11:20 ` Guennadi Liakhovetski
2011-02-28 13:44 ` Sakari Ailus
2011-03-03 7:09 ` Kim, HeungJun
2011-03-03 7:30 ` Guennadi Liakhovetski
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=1298900024.2137.31.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=g.liakhovetski@gmx.de \
--cc=hansverk@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=riverful@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=snjw23@gmail.com \
--cc=svarbanov@mm-sol.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