From: Michael Jones <michael.jones@matrix-vision.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
Subject: Re: [RFC] omap3-isp G_FMT & ENUM_FMT
Date: Fri, 27 Jul 2012 13:31:59 +0200 [thread overview]
Message-ID: <50127C2F.3080509@matrix-vision.de> (raw)
In-Reply-To: <1772349.addfYp7k4f@avalon>
Hi Laurent,
On 07/27/2012 11:35 AM, Laurent Pinchart wrote:
> On Friday 27 July 2012 11:07:50 Michael Jones wrote:
>> Hi Laurent,
>>
>> On 07/27/2012 01:32 AM, Laurent Pinchart wrote:
>>> Hi Michael,
[snip]
>> OK, so this sounds like the same behavior I'd like to add before
>> CREATE_BUFS and PREPARE_BUFS support is in. My other question was if
>> this is the case, can we use my approach until your planned changes are in?
>
> We can't, as it would break the use case of preallocating buffers without
> providing any alternative solution. That's why I haven't fixed the
> G_FMT/S_FMT/ENUM_FMT issue yet.
>
OK, now I understand. Thanks for clarifying.
-Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier
prev parent reply other threads:[~2012-07-27 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 11:59 [RFC] omap3-isp G_FMT & ENUM_FMT Michael Jones
2012-07-26 11:59 ` [PATCH 1/2] [media] omap3isp: implement ENUM_FMT Michael Jones
2012-07-26 11:59 ` [PATCH 2/2] [media] omap3isp: support G_FMT Michael Jones
2012-07-26 12:10 ` [RFC] omap3-isp G_FMT & ENUM_FMT Hans Verkuil
2012-07-26 14:05 ` Laurent Pinchart
2012-07-26 14:22 ` Michael Jones
2012-07-26 23:32 ` Laurent Pinchart
2012-07-27 9:07 ` Michael Jones
2012-07-27 9:35 ` Laurent Pinchart
2012-07-27 11:31 ` Michael Jones [this message]
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=50127C2F.3080509@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).