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

ui/gfx/gl/gl_context_egl.h

Index: ui/gfx/gl/gl_context_egl.h
diff --git a/ui/gfx/gl/gl_context_egl.h b/ui/gfx/gl/gl_context_egl.h
index 7c8c62c8e7e654bca392a0284def151a68c9b9f8..a3291e6db0cf77453c40fc8cce7f4ce60516665d 100644
--- a/ui/gfx/gl/gl_context_egl.h
+++ b/ui/gfx/gl/gl_context_egl.h
@@ -33,6 +33,7 @@ class GLContextEGL : public GLContext {
   virtual void ReleaseCurrent(GLSurface* surface) OVERRIDE;
   virtual bool IsCurrent(GLSurface* surface) OVERRIDE;
   virtual void* GetHandle() OVERRIDE;
+  virtual EGLDisplay GetDisplay() OVERRIDE;

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

I think the ui/ part of this CL should be pulled out and be its own CL (since
it's so independent).

However, it's not clear to me you need these changes, anyway.
In both GLX/EGL the relevant display is a static property, which you can get
with
base::MessagePumpForUI::GetDefaultXDisplay();
and
eglGetDisplay(EGL_DEFAULT_DISPLAY);
resp.

(also, AFAICT, you only actually use the GLX version, so the EGL edit is
completely unneeded?)

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

Yes, it will be the case in the final CL, just didn't want to give you something
that wouldn't compile and my understanding was that I can't have dependencies
between CLs here, can I?

[Ami GONE FROM CHROMIUM, 2012/03/22 17:01:36]

My CR process doesn't (usually) include compiling the change under review.
You can have chained CLs; SOP is to mention in the review message that this CL
depends on another CL(s).
(as I mentioned in my last email, it's possible to specify which diff/baselines
you want git cl upload to use)

   virtual void SetSwapInterval(int interval) OVERRIDE;
   virtual std::string GetExtensions() OVERRIDE;