From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [RFC] V4L2 codecs in user space
Date: Tue, 09 Jun 2015 10:04:13 +0900 [thread overview]
Message-ID: <55763B8D.4060107@igel.co.jp> (raw)
In-Reply-To: <1433771439.480.2.camel@collabora.com>
Hi Nicolas,
On 2015-06-08 10:50 PM, Nicolas Dufresne wrote:
> Le lundi 08 juin 2015 à 13:42 +0900, Damian Hobson-Garcia a écrit
> :
>> Also, if this method is not recommended, should there be a 1-2
>> line disclaimer on the "V4L2_Userspace_Library" wiki page that
>> mentions this?
>
> I think you may have got that wrong. The V4L2 userspace library is
> not implementing any device drivers. It allow older software to
> work with latest V4L2 features by emulating what is possible. It
> also implement platform specific setups (media controller) and
> eventually will contain needed parsers that would otherwise
> represent a security threat if ran inside the Linux Kernel.
>
Just to verify that we're on the same page, but it sounds to me that
what you're describing is the libv4l library, whereas what I was
originally referring to was the section under "A solution" at
http://linuxtv.org/wiki/index.php/V4L2_Userspace_Library
that talks about a FUSE interface to a daemon running in a different
process. Or perhaps we're both talking about the same thing. That
page also seems to mention that something like libv4l would be the
ideal solution, but that it does not exist (it's an old page).
Thank you,
Damian
> Nicolas
>
prev parent reply other threads:[~2015-06-09 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 1:40 [RFC] V4L2 codecs in user space Damian Hobson-Garcia
2015-06-08 4:42 ` Damian Hobson-Garcia
2015-06-08 8:25 ` Hans Verkuil
2015-06-08 9:54 ` Damian Hobson-Garcia
2015-06-08 10:04 ` Hans Verkuil
2015-06-10 8:17 ` Enrico Weigelt, metux IT consult
2015-06-10 8:40 ` Damian Hobson-Garcia
2015-06-08 13:50 ` Nicolas Dufresne
2015-06-09 1:04 ` Damian Hobson-Garcia [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=55763B8D.4060107@igel.co.jp \
--to=dhobsong@igel.co.jp \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.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.