meye.rst 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  1. .. include:: <isonum.txt>
  2. Vaio Picturebook Motion Eye Camera Driver
  3. =========================================
  4. Copyright |copy| 2001-2004 Stelian Pop <stelian@popies.net>
  5. Copyright |copy| 2001-2002 Alcôve <www.alcove.com>
  6. Copyright |copy| 2000 Andrew Tridgell <tridge@samba.org>
  7. This driver enable the use of video4linux compatible applications with the
  8. Motion Eye camera. This driver requires the "Sony Laptop Extras" driver (which
  9. can be found in the "Misc devices" section of the kernel configuration utility)
  10. to be compiled and installed (using its "camera=1" parameter).
  11. It can do at maximum 30 fps @ 320x240 or 15 fps @ 640x480.
  12. Grabbing is supported in packed YUV colorspace only.
  13. MJPEG hardware grabbing is supported via a private API (see below).
  14. Hardware supported
  15. ------------------
  16. This driver supports the 'second' version of the MotionEye camera :)
  17. The first version was connected directly on the video bus of the Neomagic
  18. video card and is unsupported.
  19. The second one, made by Kawasaki Steel is fully supported by this
  20. driver (PCI vendor/device is 0x136b/0xff01)
  21. The third one, present in recent (more or less last year) Picturebooks
  22. (C1M* models), is not supported. The manufacturer has given the specs
  23. to the developers under a NDA (which allows the development of a GPL
  24. driver however), but things are not moving very fast (see
  25. http://r-engine.sourceforge.net/) (PCI vendor/device is 0x10cf/0x2011).
  26. There is a forth model connected on the USB bus in TR1* Vaio laptops.
  27. This camera is not supported at all by the current driver, in fact
  28. little information if any is available for this camera
  29. (USB vendor/device is 0x054c/0x0107).
  30. Driver options
  31. --------------
  32. Several options can be passed to the meye driver using the standard
  33. module argument syntax (<param>=<value> when passing the option to the
  34. module or meye.<param>=<value> on the kernel boot line when meye is
  35. statically linked into the kernel). Those options are:
  36. .. code-block:: none
  37. gbuffers: number of capture buffers, default is 2 (32 max)
  38. gbufsize: size of each capture buffer, default is 614400
  39. video_nr: video device to register (0 = /dev/video0, etc)
  40. Module use
  41. ----------
  42. In order to automatically load the meye module on use, you can put those lines
  43. in your /etc/modprobe.d/meye.conf file:
  44. .. code-block:: none
  45. alias char-major-81 videodev
  46. alias char-major-81-0 meye
  47. options meye gbuffers=32
  48. Usage:
  49. ------
  50. .. code-block:: none
  51. xawtv >= 3.49 (<http://bytesex.org/xawtv/>)
  52. for display and uncompressed video capture:
  53. xawtv -c /dev/video0 -geometry 640x480
  54. or
  55. xawtv -c /dev/video0 -geometry 320x240
  56. motioneye (<http://popies.net/meye/>)
  57. for getting ppm or jpg snapshots, mjpeg video
  58. Private API
  59. -----------
  60. The driver supports frame grabbing with the video4linux API,
  61. so all video4linux tools (like xawtv) should work with this driver.
  62. Besides the video4linux interface, the driver has a private interface
  63. for accessing the Motion Eye extended parameters (camera sharpness,
  64. agc, video framerate), the shapshot and the MJPEG capture facilities.
  65. This interface consists of several ioctls (prototypes and structures
  66. can be found in include/linux/meye.h):
  67. MEYEIOC_G_PARAMS and MEYEIOC_S_PARAMS
  68. Get and set the extended parameters of the motion eye camera.
  69. The user should always query the current parameters with
  70. MEYEIOC_G_PARAMS, change what he likes and then issue the
  71. MEYEIOC_S_PARAMS call (checking for -EINVAL). The extended
  72. parameters are described by the meye_params structure.
  73. MEYEIOC_QBUF_CAPT
  74. Queue a buffer for capture (the buffers must have been
  75. obtained with a VIDIOCGMBUF call and mmap'ed by the
  76. application). The argument to MEYEIOC_QBUF_CAPT is the
  77. buffer number to queue (or -1 to end capture). The first
  78. call to MEYEIOC_QBUF_CAPT starts the streaming capture.
  79. MEYEIOC_SYNC
  80. Takes as an argument the buffer number you want to sync.
  81. This ioctl blocks until the buffer is filled and ready
  82. for the application to use. It returns the buffer size.
  83. MEYEIOC_STILLCAPT and MEYEIOC_STILLJCAPT
  84. Takes a snapshot in an uncompressed or compressed jpeg format.
  85. This ioctl blocks until the snapshot is done and returns (for
  86. jpeg snapshot) the size of the image. The image data is
  87. available from the first mmap'ed buffer.
  88. Look at the 'motioneye' application code for an actual example.
  89. Bugs / Todo
  90. -----------
  91. - 'motioneye' still uses the meye private v4l1 API extensions.