|
|
[Ozone-DRI] Move framebuffer initialization into the buffer
Surface/buffer lifetimes are no longer bound by the controller. In addition,
it is possible for multiple controllers to be linked against the same surface,
making it impossible for a controller to know if the framebuffers need to be
unregistered. Thus move framebuffer initialization into the buffer object.
NOTRY=true
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=269531
|
Unified diffs |
Side-by-side diffs |
Delta from patch set |
Stats (+69 lines, -129 lines) |
Patch |
 |
M |
ui/ozone/platform/dri/dri_buffer.h
|
View
|
|
1 chunk |
+0 lines, -7 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/dri_buffer.cc
|
View
|
|
4 chunks |
+35 lines, -19 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/dri_surface_factory_unittest.cc
|
View
|
|
2 chunks |
+2 lines, -13 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/dri_surface_unittest.cc
|
View
|
1
|
5 chunks |
+16 lines, -11 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/dri_wrapper.h
|
View
|
|
2 chunks |
+3 lines, -2 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/dri_wrapper.cc
|
View
|
|
2 chunks |
+11 lines, -10 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/hardware_display_controller.h
|
View
|
|
1 chunk |
+0 lines, -3 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/hardware_display_controller.cc
|
View
|
|
3 chunks |
+0 lines, -34 lines |
0 comments
|
Download
|
|
M |
ui/ozone/platform/dri/hardware_display_controller_unittest.cc
|
View
|
|
3 chunks |
+2 lines, -30 lines |
0 comments
|
Download
|
Total messages: 6 (0 generated)
|
Chromium Code Reviews
Issue
276753003:
[Ozone-DRI] Move framebuffer initialization into the buffer (Closed)
