MJPEG acceleration for video capture using VAAPI

media/video/jpeg_decode_accelerator.cc

Index: media/video/jpeg_decode_accelerator.cc
diff --git a/media/video/jpeg_decode_accelerator.cc b/media/video/jpeg_decode_accelerator.cc
new file mode 100644
index 0000000000000000000000000000000000000000..f9c602db8f6c2426c7f6ee9f75b9abdaa39f186f
--- /dev/null
+++ b/media/video/jpeg_decode_accelerator.cc
@@ -0,0 +1,24 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "media/video/jpeg_decode_accelerator.h"
+
+#include "base/logging.h"
+
+namespace media {
+
+JpegDecodeAccelerator::~JpegDecodeAccelerator() {
+}
+
+}  // namespace media
+
+namespace base {
+
+void DefaultDeleter<media::JpegDecodeAccelerator>::operator()(

[mcasas, 2015/05/07 00:59:03]

Do we still need this generic DefaultDeleter or 
should we specialize it for VaapiJpegDecodeAccelerator
instead?

[kcwu, 2015/05/08 14:42:43]

media::JpegDecodeAccelerator::Destroy is modeled after
media::VideoDecodeAccelerator::Destroy and I want to keep them consistent.

+    void* jpeg_decode_accelerator) const {
+  static_cast<media::JpegDecodeAccelerator*>(jpeg_decode_accelerator)
+      ->Destroy();
+}
+
+}  // namespace base