| 2016-08-15 08:50:34 |
Daniel van Vugt |
bug |
|
|
added bug |
| 2016-08-15 08:52:36 |
Daniel van Vugt |
description |
Rename 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. |
Rename 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. |
|
| 2016-08-23 04:07:12 |
Daniel van Vugt |
summary |
Rename mesa-kms to gbm-kms |
mesa-kms is not Mesa-specific, so needs renaming |
|
| 2016-08-23 04:07:46 |
Daniel van Vugt |
description |
Rename 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. |
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. |
|
