On Fri, Aug 3, 2012 at 12:38 AM, Romain Guy <[email protected]> wrote: >> Well, keep in mind that you can't issue GL calls from a thread >> different than the rendering thread (well unless you play games with >> multiple EGL contexts sharing resources which doesn't even seem to >> work on the incomplete/buggy EGL implementation on Android). > > It works, WebView is (or used to) rely on this feature. You might be > running into a driver specific bug though.
That's definitely good to hear, although very few people seem to know how to achieve it. I asked about it a few weeks ago, with no reply: https://groups.google.com/forum/?fromgroups#!searchin/android-developers/egl/android-developers/BHH08ak8MRA/mXaHFPNKMl8J It came up again a couple of days ago on android-ndk in this thread: https://groups.google.com/forum/?fromgroups#!searchin/android-ndk/egl/android-ndk/V3VpH65tpqA/blOrbldg7j0J The consensus seems to be it doesn't work. Note also a link there to a Mozilla dev blog post, he also comes to the conclusion context sharing doesn't work on Android. As far as a buggy driver goes - could be. One thing I know is that the failing behaviour was consistent across a bunch of Adreno 200/SGX540 devices with Android 2.1 or 2.2. I'm not sure anymore if I specifically tested it on Xoom/Honeycomb but if I did, it did not work there either. Is there a specific incantation to make it work? From my reading of the EGL spec, it should be as simple as passing the existing context to eglMakeContext() as the shared context argument... Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
