ozone: dri: Do initial cursor set

ozone: dri: Do initial cursor set

The cursor is invisible unless set explicitly, so set a bitmap from
CursorFactoryEvdevDri upon construction.

Configuration of the cursor plane must be delayed until we've configured
the hardware, so store the bitmap on DriSurfaceFactory and set it in
RealizeAcceleratedWidget.

TEST=content_shell --ozone-platform=dri
BUG=252315
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260189

[dnicoara, 2014-03-21 21:38:35]

https://codereview.chromium.org/208553004/diff/1/ui/gfx/ozone/dri/dri_surface...
File ui/gfx/ozone/dri/dri_surface_factory.cc (right):

https://codereview.chromium.org/208553004/diff/1/ui/gfx/ozone/dri/dri_surface...
ui/gfx/ozone/dri/dri_surface_factory.cc:381: cursor_surface_->SwapBuffers();
Could we move this inside HardwareDisplayController::SetCursor? My bad for not
following the same model as PageFlip.

And could we keep it after the DRM call such that the changes to DriSurface
aren't needed anymore. This is more to keep a consistent way of referring to the
buffer we're about to scan out of.

[spang, 2014-03-26 22:26:35]

https://codereview.chromium.org/208553004/diff/1/ui/gfx/ozone/dri/dri_surface...
File ui/gfx/ozone/dri/dri_surface_factory.cc (right):

https://codereview.chromium.org/208553004/diff/1/ui/gfx/ozone/dri/dri_surface...
ui/gfx/ozone/dri/dri_surface_factory.cc:381: cursor_surface_->SwapBuffers();
On 2014/03/21 21:38:35, dnicoara wrote:
> Could we move this inside HardwareDisplayController::SetCursor? My bad for not
> following the same model as PageFlip.
> 
> And could we keep it after the DRM call such that the changes to DriSurface
> aren't needed anymore. This is more to keep a consistent way of referring to
the
> buffer we're about to scan out of.

Done.

[dnicoara, 2014-03-27 01:46:18]

lgtm

[rjkroege, 2014-03-27 17:55:45]

lgtm

[spang, 2014-03-27 18:23:07]

The CQ bit was checked by spang@chromium.org

[commit-bot: I haz the power, 2014-03-27 18:24:44]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/spang@chromium.org/208553004/40001

[commit-bot: I haz the power, 2014-03-27 21:10:28]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-03-27 21:10:29]

Retried try job too often on win_rel for step(s) content_browsertests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[spang, 2014-03-28 16:02:43]

The CQ bit was checked by spang@chromium.org

[commit-bot: I haz the power, 2014-03-28 16:06:18]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/spang@chromium.org/208553004/40001

[commit-bot: I haz the power, 2014-03-28 17:45:29]

Change committed as 260189