mesa-kms is not Mesa-specific, so needs renaming
Bug #1613207 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
New
|
Undecided
|
Unassigned | ||
mir (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
mesa-kms is not Mesa-specific, so needs renaming. I suggest renaming mesa-kms to gbm-kms.
For a long time it wasn't clear which name was more appropriate but now it is. I have seen one OEM implement Wayland support for their proprietary hardware as custom binaries completely replacing the Mesa binaries:
libgbm.so.1
libEGL.so.1
libGLESv2.so.2
It works, and it should work for Mir too. So in this way our driver 'mesa-kms' should more accurately be called 'gbm-kms'. Because we are not bound to a specific "Mesa" library, just to GBM ABI level 1. And the driver gbm-kms (formerly known as mesa-kms) should transparently support non-Mesa implementations of GBM.
description: | updated |
summary: |
- Rename mesa-kms to gbm-kms + mesa-kms is not Mesa-specific, so needs renaming |
description: | updated |
To post a comment you must log in.
It'll work for the server half of the platform - we'll be able to bring up a Mir server on those drivers - clients won't have EGL support, right?