Comment 2 for bug 1550371

Basically, we're falling back to software compositing on Freiza for a couple of reasons:

- We don't set up a share context on devices where Chromium uses virtual GL contexts (essentially, all client-side GL contexts are backed by one single GL context on the GPU service side), as this is normally done to work around share-group related driver bugs.
- The graphics driver isn't advertising the extensions we require for the EGLImage compositing path (EGL_KHR_image, EGL_KHR_image_base and EGL_KHR_gl_texture_2D_image).

This means that neither of the 2 accelerated compositing paths that Oxide has available currently work on this device.