We also have a rather confusing pair of buffer classes that are nearly the same thing - GbmBuffer and GbmPixmap.
We could split things out as follows:
- GbmBuffer wraps a gbm_bo and contains no DRM master specifics
- GbmPixmap owns a GbmBuffer and adds the presentation parts
(i.e. adding framebuffers to DRM, and scheduling them with the page flip)
Removing the DRM-master bits from GbmBuffer would also mean we can move it to //ui/ozone/common/ and share it with wayland.
Comment 1 by bugdroid1@chromium.org
, Jul 31