From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.nokia.com ([147.243.128.24]:23262 "EHLO mgw-da01.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755227Ab1BJKEw (ORCPT ); Thu, 10 Feb 2011 05:04:52 -0500 Message-ID: <4D53B892.6070405@maxwell.research.nokia.com> Date: Thu, 10 Feb 2011 12:06:10 +0200 From: Sakari Ailus MIME-Version: 1.0 To: "Wang, Wen W" CC: Hans Verkuil , Jozef Kruger , "Kanigeri, Hari K" , "Iyer, Sundar" , "Yang, Jianwei" , "linux-media@vger.kernel.org" Subject: Re: Memory allocation in Video4Linux References: <201102090851.41789.hverkuil@xs4all.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-ID: Sender: Wang, Wen W wrote: > Hi Hans, > > Thanks for your point and videobuf2 is also what I want to use. > > But since our development kernel version right now is still 2.6.35, I > need to find way to work with current videobuf framework. Hi Wen, If you're bound to use that kernel version, then one option to consider might be backporting the videobuf2 to that kernel. 2.6.35 isn't so old. You'd save work by not implementing the buffer handling on your own AND also, you wouldn't later need to port the driver to use videobuf2. I would suggest not to start using the old videobuf at this point. With the current ISPs with their own MMUs it really does more harm than good. Regards, -- Sakari Ailus sakari.ailus@maxwell.research.nokia.com