Kyle Brenneman

Done.

Rebased and renumbered. I also updated the issues section to say "Resolved" instead of "Proposed resolution."

In practice, I expect that most applications and libraries would use `EGL_EXT_display_alloc` instead of `EGL_KHR_display_reference`, not use the two of them together. The main purpose of `EGL_KHR_display_reference` is so that...

> Cool, sounds good. Just checking, the difference between `eglDestroyDisplayEXT` and `eglTerminate` is that it doesn't allow reviving the display? If so, that's exactly what I wanted I think. Thanks!...

You can create two EGLDisplays from the same wl_display, but they're still separate EGLDisplays. Remember, an EGLDisplay is the namespace that EGLContexts, EGLSurfaces, and other EGL objects belong to. Every...

"Private" in this case means private to whatever called eglGetPlatformDisplay, rather than the default behavior where everything that calls eglGetPlatformDisplay would end up with the same shared EGLDisplay object. The...

Yeah, that's correct.

Can do. For the enum name, would something like "EGL_UNIQUE_DISPLAY_EXT" or "EGL_ALLOC_DISPLAY_EXT" read better than "EGL_PRIVATE_DISPLAY_EXT"?

Would it make sense to add queries for the domain/bus/slot ID's as well?

One use I can think of would be to distinguish between multiple identical devices.