[ozone/wayland] Establish BufferManagerGpu and BufferManagetHost pipe.
Previously, the WaylandConnection was a proxy between the clients of the WaylandBufferManager and the manager itself. This was a redundant functionality, and it was decided to avoid proxying. The following changes have been made in this cl: Renamed: * WaylandBufferManager => WaylandBufferManagerHost * WaylandConnectionProxy => WaylandBufferManagerGpu * WaylandConnectionConnector => WaylandBufferManagerConnector Code changes: The WaylandConnection no longer forwards calls to the WaylandBufferManager. Instead, the WaylandBufferManagerHost and the WaylandBufferManagerGpu have an associated mojo connection, and are able to speak to each other without a proxy in between. This is more logical and makes the WaylandConnection class be less overloaded with different functionality. The tests have also been rewritten, and helper methods have been added. Bug: 947411 Change-Id: I9ffd162f8459705ae22f55a9f1b1e7caa1567986 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617359Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#664678}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment