Add VAVDA, the VAAPI Video Decode Accelerator for Intel CPUs.

content/public/common/content_switches.cc

Index: content/public/common/content_switches.cc
diff --git a/content/public/common/content_switches.cc b/content/public/common/content_switches.cc
index ac88386ca46f3799ca393d449363e2a404c992b3..b9342b545ee2a2c82243743ef7a750fdc23af400 100644
--- a/content/public/common/content_switches.cc
+++ b/content/public/common/content_switches.cc
@@ -337,6 +337,10 @@ const char kEnableTcpFastOpen[]             = "enable-tcp-fastopen";
 // Enable support for JavaScript touch events.
 const char kEnableTouchEvents[]             = "enable-touch-events";
 
+// Enables hardware acceleration for video decode on Linux and ChromeOS
+// on Intel CPUs (mostly Sandy Bridge+) using VAAPI.
+const char kEnableVaapiDecodeAcceleration[] = "enable-vaapi-decode-accel";

[Ami GONE FROM CHROMIUM, 2012/03/21 13:16:24]

Can VAAPI be used for anything other than video decode acceleration?
I think a better flag name would be --enable-vaapi / kEnableVaapi

[Pawel Osciak, 2012/03/21 18:40:35]

No
Ok

+
 // Enables support for video tracks. Current implementation is
 // incomplete and this flag is used for development and testing.
 const char kEnableVideoTrack[]              = "enable-video-track";