Implement OSMesa image transport for TOUCH_UI builds

chrome/browser/renderer_host/render_widget_host_view_mac.mm

Index: chrome/browser/renderer_host/render_widget_host_view_mac.mm
diff --git a/chrome/browser/renderer_host/render_widget_host_view_mac.mm b/chrome/browser/renderer_host/render_widget_host_view_mac.mm
index 46fad6e7ed0a97d36a2ad4e8eb637977cfa9938f..65845912690c4cebf5d2f4c8fd48167a205a5225 100644
--- a/chrome/browser/renderer_host/render_widget_host_view_mac.mm
+++ b/chrome/browser/renderer_host/render_widget_host_view_mac.mm
@@ -878,7 +878,7 @@ AcceleratedPluginView* RenderWidgetHostViewMac::ViewForPluginWindowHandle(
   return it->second;
 }
 
-void RenderWidgetHostViewMac::AcceleratedSurfaceSetIOSurface(
+void RenderWidgetHostViewMac::AcceleratedSurfaceNew(

[jonathan.backer, 2011/09/21 20:27:36]

I'm not sure it makes sense to rename this yet. Currently, it's always an
IOSurface -- and it's being initialized in the GPU process.

[danakj, 2011/09/21 20:58:20]

To have a different name means a number of places need to be copied that are
currently OS_MACOSX || TOUCH_UI.  Unless the touch one remains SetIOSurface (I
am against that).

For instance: gpu_messages.h, and
content/browser/gpu/gpu_process_host_ui_shim.cc:243

     gfx::PluginWindowHandle window,
     int32 width,
     int32 height,