From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Damian Hobson-Garcia <dhobsong@igel.co.jp>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [RFC] V4L2 codecs in user space
Date: Mon, 08 Jun 2015 09:50:39 -0400 [thread overview]
Message-ID: <1433771439.480.2.camel@collabora.com> (raw)
In-Reply-To: <55751D44.6010102@igel.co.jp>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
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.
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-06-08 13:50 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 [this message]
2015-06-09 1:04 ` Damian Hobson-Garcia
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=1433771439.480.2.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=dhobsong@igel.co.jp \
--cc=linux-media@vger.kernel.org \
/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).