From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "Wang, Wen W" <wen.w.wang@intel.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Jozef Kruger <jozef.kruger@siliconhive.com>,
"Kanigeri, Hari K" <hari.k.kanigeri@intel.com>,
"Iyer, Sundar" <sundar.iyer@intel.com>,
"Yang, Jianwei" <jianwei.yang@intel.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Memory allocation in Video4Linux
Date: Thu, 10 Feb 2011 12:06:10 +0200 [thread overview]
Message-ID: <4D53B892.6070405@maxwell.research.nokia.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A32F92475@shsmsx501.ccr.corp.intel.com>
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
next prev parent reply other threads:[~2011-02-10 10:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 6:23 Memory allocation in Video4Linux Wang, Wen W
2011-02-09 6:30 ` Kanigeri, Hari K
2011-02-09 6:30 ` Yang, Jianwei
2011-02-09 6:32 ` Wang, Wen W
2011-02-09 6:49 ` Iyer, Sundar
2011-02-09 7:22 ` Kanigeri, Hari K
2011-02-09 7:27 ` Wang, Wen W
2011-02-09 7:51 ` Hans Verkuil
2011-02-09 7:55 ` Wang, Wen W
2011-02-10 10:06 ` Sakari Ailus [this message]
2011-02-09 7:58 ` Jonghun Han
2011-02-09 8:10 ` Wang, Wen W
2011-02-10 7:59 ` Gao, Bin
2011-02-10 8:08 ` Jozef Kruger
2011-02-10 9:29 ` Laurent Pinchart
2011-02-10 9:44 ` Wang, Wen W
2011-02-10 10:00 ` Laurent Pinchart
2011-02-11 2:07 ` KyongHo Cho
2011-02-09 10:19 ` 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=4D53B892.6070405@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=hari.k.kanigeri@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jianwei.yang@intel.com \
--cc=jozef.kruger@siliconhive.com \
--cc=linux-media@vger.kernel.org \
--cc=sundar.iyer@intel.com \
--cc=wen.w.wang@intel.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