VaapiVideoAccelerator: make Vaapi accelerator work with ozone

ui/ozone/platform/dri/ozone_platform_gbm.cc

Index: ui/ozone/platform/dri/ozone_platform_gbm.cc
diff --git a/ui/ozone/platform/dri/ozone_platform_gbm.cc b/ui/ozone/platform/dri/ozone_platform_gbm.cc
index 344422ba9e55fa0103fa569d8127ea1180857481..8c5560c805c4742f3c1dbb9e36197a578f21c33a 100644
--- a/ui/ozone/platform/dri/ozone_platform_gbm.cc
+++ b/ui/ozone/platform/dri/ozone_platform_gbm.cc
@@ -115,7 +115,8 @@ class OzonePlatformGbm : public OzonePlatform {
     vt_manager_.reset(new VirtualTerminalManager());
     // Needed since the browser process creates the accelerated widgets and that
     // happens through SFO.
-    surface_factory_ozone_.reset(new GbmSurfaceFactory(use_surfaceless_));
+    if (!surface_factory_ozone_)

[kalyank, 2014/11/01 19:28:35]

Why is this needed ?

[llandwerlin-old, 2014/11/03 09:30:11]

We don't want to initialize the surface factory twice (when calling InitializeUI
and InitializeGPU).

[kalyank, 2014/11/04 01:04:19]

This should be the case only when in single process mode, other wise we should
be initializing them in different process (InitializeUI should be called from
Browser process and GPU from GPU process respectively.) Even in single process
case, UI should be called first and then GPU. I think we should avoid this
change as part of this CL and move it to a separate CL.
spang ^

[dnicoara, 2014/11/04 01:26:27]

When running in-process, InitializeUI() should be called first, that's why the
if-statement is present in InitializeGPU().

[kalyank, 2014/11/04 16:45:10]

Ya, so we don't need this change basically.

+      surface_factory_ozone_.reset(new GbmSurfaceFactory(use_surfaceless_));
     device_manager_ = CreateDeviceManager();
     gpu_platform_support_host_.reset(new DriGpuPlatformSupportHost());
     cursor_factory_ozone_.reset(new BitmapCursorFactoryOzone);