New Pepper interfaces for audio/video capture device enumeration.

ppapi/api/dev/ppb_video_capture_dev.idl

Index: ppapi/api/dev/ppb_video_capture_dev.idl
diff --git a/ppapi/api/dev/ppb_video_capture_dev.idl b/ppapi/api/dev/ppb_video_capture_dev.idl
old mode 100644
new mode 100755
index c60f9573ae74ed2d9ee0e45b6e86b5e10d29fa5b..c81390d7e545215201211755856310c677687db1
--- a/ppapi/api/dev/ppb_video_capture_dev.idl
+++ b/ppapi/api/dev/ppb_video_capture_dev.idl
@@ -7,7 +7,8 @@
  * This file defines the <code>PPB_VideoCapture_Dev</code> interface.
  */
 label Chrome {
-  M14 = 0.1
+  M14 = 0.1,
+  M18 = 0.2
 };
 
 /**
@@ -67,6 +68,27 @@ interface PPB_VideoCapture_Dev {
       [in] uint32_t buffer_count);
 
   /**
+   * Starts the capture. |device_ref| identifies a video capture device,
+   * returned by <code>PPB_DeviceEnumerator_Dev</code>. |requested_info| is a
+   * pointer to a structure containing the requested resolution and frame rate.
+   * |buffer_count| is the number of buffers requested by the plugin. Note: it
+   * is only used as advisory, the browser may allocate more of fewer based on
+   * available resources. How many buffers depends on usage. At least 2 to make
+   * sure latency doesn't cause lost frames. If the plugin expects to hold on to
+   * more than one buffer at a time (e.g. to do multi-frame processing, like
+   * video encoding), it should request that many more.
+   *
+   * Returns PP_ERROR_FAILED if called when the capture was already started, or
+   * PP_OK on success.
+   */
+  [version=0.2]
+  int32_t StartCapture(
+      [in] PP_Resource video_capture,
+      [in] PP_Resource device_ref,
+      [in] PP_VideoCaptureDeviceInfo_Dev requested_info,
+      [in] uint32_t buffer_count);
+
+  /**
    * Allows the browser to reuse a buffer that was previously sent by
    * PPP_VideoCapture_Dev.OnBufferReady. |buffer| is the index of the buffer in
    * the array returned by PPP_VideoCapture_Dev.OnDeviceInfo.