From: Yordan Kamenov <ykamenov@mm-sol.com>
To: hdegoede@redhat.com
Cc: linux-media@vger.kernel.org,
sakari.ailus@maxwell.research.nokia.com,
Yordan Kamenov <ykamenov@mm-sol.com>
Subject: [PATCH 0/1] libv4l: Add plugin support
Date: Fri, 7 Jan 2011 18:59:34 +0200 [thread overview]
Message-ID: <cover.1294418213.git.ykamenov@mm-sol.com> (raw)
Hi Hans,
Here is initial version of plugin support for libv4l, based on your RFC.
It is provided by functions v4l2_plugin_[open,close,etc]. When open() is
called libv4l dlopens files in /usr/lib/libv4l/plugins 1 at a time and call
open() callback passing through the applications parameters unmodified.
If a plugin is relevant for the specified device node, it can indicate so by
returning a value other then -1 (the actual file descriptor).
As soon as a plugin returns another value then -1 plugin loading stops and
information about it (fd and corresponding library handle) is stored.
For each function v4l2_[ioctl,read,close,etc] is called corresponding
v4l2_plugin_* function which looks if there is loaded plugin for that file
and call it's callbacks. v4l2_plugin_* functions indicate by their first
argument if plugin was used, and if it was not then v4l2_* functions proceed
with their usual behavior.
Yordan Kamenov (1):
Add plugin support to libv4l
lib/include/libv4l2-plugin.h | 74 ++++++++
lib/include/libv4l2.h | 15 ++
lib/libv4l2/Makefile | 4 +-
lib/libv4l2/libv4l2-priv.h | 9 +
lib/libv4l2/libv4l2.c | 56 ++++++-
lib/libv4l2/v4l2-plugin.c | 399 ++++++++++++++++++++++++++++++++++++++++++
lib/libv4l2/v4l2convert.c | 20 ++-
7 files changed, 568 insertions(+), 9 deletions(-)
create mode 100644 lib/include/libv4l2-plugin.h
create mode 100644 lib/libv4l2/v4l2-plugin.c
--
1.7.3.1
next reply other threads:[~2011-01-07 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 16:59 Yordan Kamenov [this message]
2011-01-07 16:59 ` [PATCH 1/1] Add plugin support to libv4l Yordan Kamenov
2011-01-08 19:12 ` Hans de Goede
2011-01-11 13:58 ` Yordan Kamenov
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=cover.1294418213.git.ykamenov@mm-sol.com \
--to=ykamenov@mm-sol.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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