From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Pawel Osciak <pawel@osciak.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH v3] V4L: add two new ioctl()s for multi-size videobuffer management
Date: Sat, 30 Jul 2011 19:06:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1107301850130.12984@axis700.grange> (raw)
In-Reply-To: <201107301550.53638.hverkuil@xs4all.nl>
On Sat, 30 Jul 2011, Hans Verkuil wrote:
> On Saturday, July 30, 2011 06:21:37 Pawel Osciak wrote:
[snip]
> > So when the driver sees a larger buffer being queued, it is
> > to change the current streaming format for the duration of filling
> > that buffer and switch back afterwards?
>
> No. We do not have a mechanism (yet) to tie a pipeline configuration to
> a queued buffer (to be discussed in next week in Cambourne).
>
> It is my understanding that you change the current streaming format, and
> then queue the large (prepared) buffer and switch back afterwards.
Yes, this is also how I see it - the driver just has a chance to verify,
whether the queued buffer is not large enough for the current format and
fail QBUF, although this behaviour is currently not documented in the QBUF
specification...
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2011-07-30 17:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 8:43 [PATCH v3] V4L: add two new ioctl()s for multi-size videobuffer management Guennadi Liakhovetski
2011-07-20 14:30 ` Sakari Ailus
2011-07-20 14:47 ` Guennadi Liakhovetski
2011-07-20 15:19 ` Sakari Ailus
2011-07-26 11:05 ` Hans Verkuil
2011-07-26 11:44 ` Sakari Ailus
2011-07-26 11:57 ` Hans Verkuil
2011-08-01 8:42 ` Guennadi Liakhovetski
2011-08-01 14:55 ` Sakari Ailus
2011-08-01 15:05 ` Guennadi Liakhovetski
2011-08-02 8:08 ` Sakari Ailus
2011-08-02 8:20 ` Guennadi Liakhovetski
2011-08-02 10:45 ` Sakari Ailus
2011-08-02 11:11 ` Guennadi Liakhovetski
2011-08-02 13:46 ` Sakari Ailus
2011-08-02 14:28 ` Guennadi Liakhovetski
2011-07-28 10:26 ` Guennadi Liakhovetski
2011-07-26 10:41 ` Hans Verkuil
2011-07-27 13:11 ` Sylwester Nawrocki
2011-07-28 10:28 ` Guennadi Liakhovetski
2011-07-28 4:11 ` Pawel Osciak
2011-07-28 6:56 ` Hans Verkuil
2011-07-28 12:29 ` Guennadi Liakhovetski
2011-07-28 12:42 ` Hans Verkuil
2011-07-29 7:59 ` Sakari Ailus
2011-07-30 4:21 ` Pawel Osciak
2011-07-30 13:50 ` Hans Verkuil
2011-07-30 17:06 ` Guennadi Liakhovetski [this message]
2011-08-01 10:55 ` Guennadi Liakhovetski
2011-08-02 8:15 ` Guennadi Liakhovetski
2011-08-02 8:33 ` Hans Verkuil
2011-08-03 15:29 ` Hans Verkuil
2011-08-03 22:18 ` Guennadi Liakhovetski
2011-08-04 8:57 ` Sakari Ailus
2011-08-02 21:38 ` Sakari Ailus
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=Pine.LNX.4.64.1107301850130.12984@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=pawel@osciak.com \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@maxwell.research.nokia.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.