From: Sylwester Nawrocki <snjw23@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: Embedded device and the V4L2 API support - Was: [GIT PATCHES FOR 3.1] s5p-fimc and noon010pc30 driver updates
Date: Sat, 20 Aug 2011 13:27:07 +0200 [thread overview]
Message-ID: <4E4F9A0B.4050302@gmail.com> (raw)
In-Reply-To: <4E4B5C27.3000008@redhat.com>
Hi Mauro,
On 08/17/2011 08:13 AM, Mauro Carvalho Chehab wrote:
> It seems that there are too many miss understandings or maybe we're just
> talking the same thing on different ways.
>
> So, instead of answering again, let's re-start this discussion on a
> different way.
>
> One of the requirements that it was discussed a lot on both mailing
> lists and on the Media Controllers meetings that we had (or, at least
> in the ones where I've participated) is that:
>
> "A pure V4L2 userspace application, knowing about video device
> nodes only, can still use the driver. Not all advanced features
> will be available."
What does a term "a pure V4L2 userspace application" mean here ?
Does it also account an application which is linked to libv4l2 and uses
calls specific to a particular hardware which are included there?
>
> This is easily said than done. Also, different understandings can be
> obtained by a simple phrase like that.
--
Regards,
Sylwester
next prev parent reply other threads:[~2011-08-20 11:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 16:35 [GIT PATCHES FOR 3.1] s5p-fimc and noon010pc30 driver updates Sylwester Nawrocki
2011-07-28 2:55 ` Mauro Carvalho Chehab
2011-07-28 10:09 ` Sylwester Nawrocki
2011-07-28 13:20 ` Mauro Carvalho Chehab
2011-07-28 22:57 ` Sylwester Nawrocki
2011-07-29 4:02 ` Mauro Carvalho Chehab
2011-07-29 8:36 ` Laurent Pinchart
2011-08-09 20:05 ` Mauro Carvalho Chehab
2011-08-09 23:18 ` Sakari Ailus
2011-08-10 0:22 ` Mauro Carvalho Chehab
2011-08-10 8:41 ` Sylwester Nawrocki
2011-08-10 12:52 ` Mauro Carvalho Chehab
2011-08-15 12:45 ` Laurent Pinchart
2011-08-16 0:21 ` Mauro Carvalho Chehab
2011-08-16 8:59 ` Laurent Pinchart
2011-08-16 15:07 ` Mauro Carvalho Chehab
2011-08-15 12:30 ` Laurent Pinchart
2011-08-16 0:13 ` Mauro Carvalho Chehab
2011-08-16 8:57 ` Laurent Pinchart
2011-08-16 15:30 ` Mauro Carvalho Chehab
2011-08-16 15:44 ` Laurent Pinchart
2011-08-16 22:36 ` Mauro Carvalho Chehab
2011-08-17 7:57 ` Laurent Pinchart
2011-08-17 12:25 ` Mauro Carvalho Chehab
2011-08-17 12:37 ` Ivan T. Ivanov
2011-08-17 13:27 ` Mauro Carvalho Chehab
2011-08-17 12:33 ` Sakari Ailus
2011-08-16 21:47 ` Sylwester Nawrocki
2011-08-17 6:13 ` Embedded device and the V4L2 API support - Was: " Mauro Carvalho Chehab
2011-08-20 11:27 ` Sylwester Nawrocki [this message]
2011-08-20 12:12 ` Mauro Carvalho Chehab
2011-08-24 22:29 ` Sakari Ailus
2011-08-25 12:43 ` Mauro Carvalho Chehab
2011-08-26 13:45 ` Laurent Pinchart
2011-08-26 14:16 ` Hans Verkuil
2011-08-26 15:09 ` Mauro Carvalho Chehab
2011-08-26 15:29 ` Hans Verkuil
2011-08-26 17:32 ` Mauro Carvalho Chehab
2011-08-29 9:24 ` Laurent Pinchart
2011-08-29 14:53 ` Mauro Carvalho Chehab
2011-08-29 9:12 ` Laurent Pinchart
2011-08-30 20:34 ` Sakari Ailus
2011-08-03 14:28 ` Sylwester Nawrocki
2011-07-29 8:17 ` 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=4E4F9A0B.4050302@gmail.com \
--to=snjw23@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
/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