Comment 1 for bug 1258579

So, reading the spec (specifically, section 3.7), I believe the current mesa behaviour is wrong and you should be perfectly able to eglMakeCurrent(context). Indeed, it looks like you should even be able to call SwapBuffers on thread 2 even without making a context current there.

However, I don't think the proposed solution is correct, either; as I read the spec we actually need the the context (and surface) to have a reference to their own API index, separate to the thread's API index - you can have multiple contexts of different APIs active on a same thread.

To the mesa devel lists!