cc: Changes to use GL API for GpuMemoryBuffers

cc/trees/layer_tree_host_impl.cc

Index: cc/trees/layer_tree_host_impl.cc
diff --git a/cc/trees/layer_tree_host_impl.cc b/cc/trees/layer_tree_host_impl.cc
index 98bafc37599e18271d7c51d5861455e7ab1deeb3..04f1f105747ab69613a53dcc0a81693b27a4d62a 100644
--- a/cc/trees/layer_tree_host_impl.cc
+++ b/cc/trees/layer_tree_host_impl.cc
@@ -1389,7 +1389,8 @@ bool LayerTreeHostImpl::InitializeRenderer(
                                         settings_.num_raster_threads,
                                         settings_.use_color_estimator,
                                         settings_.prediction_benchmarking,
-                                        rendering_stats_instrumentation_));
+                                        rendering_stats_instrumentation_,
+                                        settings_.use_map_image));

[reveman, 2013/05/22 18:56:41]

settings_.use_map_image doesn't seem to take output surface capabilities() into
account. am I missing something or should you be using
output_surface->capabilities().using_map_image here?

[kaanb, 2013/05/22 19:13:03]

We plan to use a command flag to initially control this feature. After that the
plan is to enable it by default for WebView. 

[reveman, 2013/05/22 19:51:19]

but shouldn't it be "settings_.use_map_image && capabilities().using_map_image"?
I don't understand what the capabilities part is about otherwise.

[kaanb, 2013/05/22 20:21:01]

Okay, I'm using RendererCapabilities, not OutputSurface capabilities.

Please take another look.

     UpdateTileManagerMemoryPolicy(managed_memory_policy_);
   }