New Pepper interfaces for audio/video capture device enumeration.

ppapi/c/dev/ppb_video_capture_dev.h

Index: ppapi/c/dev/ppb_video_capture_dev.h
diff --git a/ppapi/c/dev/ppb_video_capture_dev.h b/ppapi/c/dev/ppb_video_capture_dev.h
index 6c3beb3eb510b17e9cd21293688c517853698e2a..0d87ebc4f624d82b4ad4cdc98abbee47ba3444ab 100644
--- a/ppapi/c/dev/ppb_video_capture_dev.h
+++ b/ppapi/c/dev/ppb_video_capture_dev.h
@@ -3,7 +3,7 @@
  * found in the LICENSE file.
  */
 
-/* From dev/ppb_video_capture_dev.idl modified Wed Oct  5 09:11:07 2011. */
+/* From dev/ppb_video_capture_dev.idl modified Mon Dec 19 10:53:24 2011. */
 
 #ifndef PPAPI_C_DEV_PPB_VIDEO_CAPTURE_DEV_H_
 #define PPAPI_C_DEV_PPB_VIDEO_CAPTURE_DEV_H_
@@ -16,7 +16,8 @@
 #include "ppapi/c/pp_stdint.h"
 
 #define PPB_VIDEOCAPTURE_DEV_INTERFACE_0_1 "PPB_VideoCapture(Dev);0.1"
-#define PPB_VIDEOCAPTURE_DEV_INTERFACE PPB_VIDEOCAPTURE_DEV_INTERFACE_0_1
+#define PPB_VIDEOCAPTURE_DEV_INTERFACE_0_2 "PPB_VideoCapture(Dev);0.2"
+#define PPB_VIDEOCAPTURE_DEV_INTERFACE PPB_VIDEOCAPTURE_DEV_INTERFACE_0_2
 
 /**
  * @file
@@ -63,20 +64,22 @@ struct PPB_VideoCapture_Dev {
    */
   PP_Bool (*IsVideoCapture)(PP_Resource video_capture);
   /**
-   * Starts the capture. |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.
+   * 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.
    */
   int32_t (*StartCapture)(
       PP_Resource video_capture,
+      PP_Resource device_ref,
       const struct PP_VideoCaptureDeviceInfo_Dev* requested_info,
       uint32_t buffer_count);
   /**
@@ -97,6 +100,17 @@ struct PPB_VideoCapture_Dev {
    */
   int32_t (*StopCapture)(PP_Resource video_capture);
 };
+
+struct PPB_VideoCapture_Dev_0_1 {
+  PP_Resource (*Create)(PP_Instance instance);
+  PP_Bool (*IsVideoCapture)(PP_Resource video_capture);
+  int32_t (*StartCapture)(
+      PP_Resource video_capture,
+      const struct PP_VideoCaptureDeviceInfo_Dev* requested_info,
+      uint32_t buffer_count);
+  int32_t (*ReuseBuffer)(PP_Resource video_capture, uint32_t buffer);
+  int32_t (*StopCapture)(PP_Resource video_capture);
+};
 /**
  * @}
  */