Monday, February 18, 2013

Opera moves to Webkit, and performance on AM335x

Opera moves to Webkit. Now there are 3 major web engines to account for, 2 opensource - Webkit (Now used by Opera, Qt, Apple, Chromium), Gecko (Firefox, Forefox OS), and IE (closed platform). Other than IE, both Webkit and Gecko support WebGL.

A short comparison of what performance each of these engines give on AM335x is provided in the link below:


  1. Hi Prabindh,

    Those performance/functionality figures for the Gecko/ b2g framebuffer looks good.

    Could you please give a few hints on how you build firefox-os for AM335x?

    I assume a lot of patches are (still) involved to make it work with the EGL/GLESv2 stack on AM335x?

    Br, Martin

  2. Martin, yes - Patches are involved, but nothing specific to AM335x / GLES2, they are for adding a framebuffer renderer for Firefox.

  3. Prabindh, do you build firefox 19 or b2g / firefox-os?

    I have experience building firefox (using .mozconfig etc.) but I find it difficult to find any descriptions on how to build b2g / firefox-os - all build descriptions are Android specifc and I don't want Android :(

    All of the patches you put on github - are all of them still required?

    Again, any hints are appreciated. Thanks!


  4. Yes - This is a confusing name since Mozilla moved b2g. The fb port now should be called "linuxgl". I would not advise this for production use at this point. What would be your use-case for this ?

  5. Currently it is mainly for prototyping - basically to see if it can be used as a html5 application platform for non-mobile, in particular on the Sitara. It is okay that it is not production quality at the moment - in time we can hopefully make it ready for production. The firefox os / b2g platform has better potential on non-mobile embedded devices than Android ever had because of its modularity - I just hope that Mozilla realizes this and keeps it so. I for one, would like to help make it so.