mesa-kms is not Mesa-specific, so needs renaming

[Daniel van Vugt]

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.

[Chris Halse Rogers (raof)]

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?

[Daniel van Vugt (vanvugt)]

EGL client support is WIP.

[Chris Halse Rogers (raof)]

I'm not particularly opposed to the rename, but we have requirements greater than GBM ABI level 1 - specifically, we require EGL client library support.

[Daniel van Vugt (vanvugt)]

OK, so to be more specific you could call it 'gbm-egl-kms' or such. I'd be happy with 'gbm-kms' and just imply EGL.

[Michał Sawicz (saviq)]

Syncing task from Mir.