Hi Mauro,
The latest event patchset is available in my Gitorious tree now. The
file handles documentation patch changed due to unrelated changes in
Documentation/video4linux/v4l2-framework.txt. There are no other changes
compared to the patches sent to the list earlier.
Please pull.
The following changes since commit 9178a7c062ff0c43e95d826419f9e9454c52ef15:
Mauro Carvalho Chehab (1):
V4L/DVB: Fix bad whitespacing
are available in the git repository at:
git://gitorious.org/omap3camera/mainline.git v4l-dvb-event
Sakari Ailus (6):
V4L: File handles
V4L: File handles: Add documentation
V4L: Events: Add new ioctls for events
V4L: Events: Add backend
V4L: Events: Support event handling in do_ioctl
V4L: Events: Add documentation
Documentation/DocBook/media-entities.tmpl | 9 +
Documentation/DocBook/v4l/dev-event.xml | 31 ++
Documentation/DocBook/v4l/v4l2.xml | 3 +
Documentation/DocBook/v4l/vidioc-dqevent.xml | 124 +++++++++
.../DocBook/v4l/vidioc-subscribe-event.xml | 104 +++++++
Documentation/video4linux/v4l2-framework.txt | 97 +++++++
drivers/media/video/Makefile | 3 +-
drivers/media/video/v4l2-compat-ioctl32.c | 3 +
drivers/media/video/v4l2-dev.c | 4 +
drivers/media/video/v4l2-event.c | 289
++++++++++++++++++++
drivers/media/video/v4l2-fh.c | 79 ++++++
drivers/media/video/v4l2-ioctl.c | 53 ++++
include/linux/videodev2.h | 26 ++
include/media/v4l2-dev.h | 5 +
include/media/v4l2-event.h | 67 +++++
include/media/v4l2-fh.h | 44 +++
include/media/v4l2-ioctl.h | 7 +
17 files changed, 947 insertions(+), 1 deletions(-)
create mode 100644 Documentation/DocBook/v4l/dev-event.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-dqevent.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subscribe-event.xml
create mode 100644 drivers/media/video/v4l2-event.c
create mode 100644 drivers/media/video/v4l2-fh.c
create mode 100644 include/media/v4l2-event.h
create mode 100644 include/media/v4l2-fh.h
--
Sakari Ailus
sakari.ailus@xxxxxxxxxxxxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
