23 ms·
It's still using Android graphics stack, so it's not that exciting. Tizen at least uses X.org with plans to use Wayland which is the way forward. I hope Mozilla
by shmerl 14y ago
It's still using Android graphics stack, so it's not that exciting. Tizen at least uses X.org with plans to use Wayland which is the way forward. I hope Mozilla will find vendors to use Wayland for B2G as well. I.e. Android graphics stack (when it's the only option) prevents device from being hackable, i.e. for porting other distros on it (Mer/PlasmaActive, Nemo etc.). Tizen devices with X.org/Wayland drivers will be better in that regard.
- edderly 14y agoOn the contrary this is the smartest thing they could have done. GPU h/w acceleration on mobile devices isn't optional any more and rather than getting mired in the 'real soon now' world of Linux graphics they can get on with the job of producing real and usable devices.
- shmerl 14y agoI'm not saying that what they did isn't useful at all. I said it's not exciting, since these upcoming devices will be again Android (compatible) only. Rather boring, but it's not Mozilla's fault, but manufacturers'. They don't produce open specs for their hardware, and don't provide X.org/Wayland drivers either.
- runeks 14y ago> Tizen devices with X.org/Wayland drivers will be better in that regard. Hopefully vendors will care enough about Wayland to start making their drivers compatible with it.
- hollerith 14y ago>Wayland is the way forward Parenthetically, Google Chrome already has an alpha-quality port to Wayland whereas to my knowledge Mozilla has made no commitment to support Wayland, and no one has started porting Firefox to Wayland.
- shmerl 14y agoThere is no need for specific port. Just minor modifications in B2G in order not to depend on any Android infrastructure. It's mostly OpenGL ES dependent: https://wiki.mozilla.org/B2G/Architecture#Gecko:_Graphics https://wiki.mozilla.org/B2G/Architecture#Gecko:_Graphics Just instead of any Android layers, it'll use OpenGL ES provided with Wayland stack.
- daeken 14y agoWe really don't use the Android graphics stack. We use the drivers in the kernel, and we use the gralloc stuff, but that's about it. Everything else is Gecko's own renderer. (I work on the gfx pipeline for B2G) Edit: Oh yea, and we use Android's libegl wrapper stuff. Not that it matters, but just in the interest of correctness.
- shmerl 14y agoI was primarily referring to the drivers architecture (which is incompatible and useless for X.org and Wayland). I mean in practice, Firefox OS targeted devices won't have X.org/Wayland GPU drivers, only Android ones. It's not important for immediate goals of Mozilla, since squeezing regular Linux graphic drivers from vendors is a horror. But it doesn't help other distros (like Mer/PlasmaActive and etc.), if they decide to make ports to these devices. It may be not Mozilla's primary goal to promote conventional mobile Linux, but in practice these devices won't help that cause (at least for now), so I feel like they won't be enough of "open devices" in that sense. On the other hand, if X.org/Wayland based devices will appear (like upcoming Mer/Vivaldi tablet), Mozilla can enable B2G to run on them as well, since they'll provide sufficient support for OpenGL ES.