Merge lp:~andreas-pokorny/mir/fix-1391975 into lp:mir
Proposed by
Andreas Pokorny
Status: | Merged |
---|---|
Merged at revision: | 2125 |
Proposed branch: | lp:~andreas-pokorny/mir/fix-1391975 |
Merge into: | lp:mir |
Diff against target: |
202 lines (+79/-28) 3 files modified
src/platform/graphics/mesa/cursor.cpp (+6/-5) src/platform/graphics/mesa/cursor.h (+3/-0) tests/unit-tests/graphics/mesa/test_cursor.cpp (+70/-23) |
To merge this branch: | bzr merge lp:~andreas-pokorny/mir/fix-1391975 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Daniel van Vugt | Approve | ||
Alberto Aguirre (community) | Approve | ||
Kevin DuBois (community) | Needs Fixing | ||
Robert Carr (community) | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Andreas Pokorny (community) | Needs Information | ||
Alexandros Frantzis (community) | Needs Fixing | ||
Review via email:
|
Commit message
Uses new DRM_CAP_
Kaveri based systems seem to provide 128x128 buffers whenever GBM_BO_USE_CURSOR is requested. (LP: #1391975)
Description of the change
This change adds some DRM capability test for cursor buffers, and only uses the buffer sizes reported by gbm_bo_
To post a comment you must log in.
89 + struct CursorCapabilities ies(int connection);
90 + {
91 + CursorCapabilit
92 + uint64_t width, height;
93 + } cursor_cap;
Is there a reason to expose this in the header?