Yeap. Right now it's most likely that Jolla's first phone will be using a Mali (due to their partnerships).
Originally Posted by droidhacker
If anyone was to ever fork or rewrite Lima at some point, they should totally call it "Armali"
It seems to me that regardless of whatever marketing speak Canonical paints over this, it makes quite a bit of sense if they REALLY plan on putting Mir in "production" as soon I think I remember was stated early on (i.e. in the next year). Even if they had started trying to negotiate their own drivers as soon as they decided to go with Mir, I just don't see them getting their own special drivers in time for rollout.
I don't know if it is necessary or even possible for backport hacking to be done so that the drivers will work on cutting edge kernels, but I'm guessing that's their plan.
raspberry pi does not have mali. It has a BCM2835 broadcom videocore. And yes, it does work with accelerated UI, using evil "driver is entirely hidden in firmware" approach.
Originally Posted by TheOne
And BTW: odroid u2 is on a totally different playing field from raspberry pi. Raspberry pi has a crappy single core 700. odroid u2 has a quad-core cortex A9, with a, yes, this one actually does have a Mali.
Last edited by droidhacker; 04-09-2013 at 12:18 PM.
Could you please share the link to the source of that claim? I dont think they at least care even a bit about opensource drivers. If not the oposite.
Originally Posted by pdffs
To the news, I found the title funny, because I did ask myself never that question, but I did not read here anything about that Mir will be compatible or uses android driver architecture.
So I would have liked as title more something like: "Canonicals Mir is using Android drivers" or somethign like that.
I need no Canonical dev say some marketing blabla about it, to know why they want that.
If you as company care 0 about free software, free drivers and so on, of course you would like to be able to use all the arm non-free drivers.
If you have not to sell your "product" because of openess or freeness, you just can switch from closedsource support drivers (too) into closedsource drivers only from now on, a complete closed plattform.
From now on I think I call Ubuntu not anymore (GNU)Ubuntu/Linux, but Ubuntu/Android so Ubuntu is now a Android distribution, basicly.
And they should not say some stupid about the architecture, its because they can use the closed source drivers, thats the reason the only reason for that move.
So I am to lazy to scandalize that, I will make my desition based on that desitions and maybe some are able to guess what that is.
Last edited by blackiwid; 04-09-2013 at 12:28 PM.
If I'm correct, Mir would use the same approach as Wayland to get up and running on Android drivers through libhybris. Maybe that's an oversimplification, but for people who think this is somehow Mir's secret weapon, there's nothing to keep Wayland from the same approach. So we don't need Mir to run the traditional Linux stack (GTK & Qt in particular) on the broad range of mobile devices.
On the other hand, I get the feeling that running all of the same software on an Android GPU would give you some issues. Would Blender 'just work', for instance? Consider how Intel's GPU drivers on Mesa used to have issues and still do with some advanced features, like acceleration in VMWare and VirtualBox (probably not necessarily Intel's fault). Still, you see where I'm going with this- can we really use all the same software, even with XWayland/XMir? If so, count me in for a future in ARM.
Likely not. Many mobile GPUs only support GL ES, and even those that would support real/desktop GL, the Android drivers are ES only.
Originally Posted by scionicspectre
That is, unless Blender has a GL ES port.
I guess we will have to wait to see if Canonical's offerings triumph or become a major league disaster. I guess that part of success will be if open source developers update the source of many critical applications to use newer technologies Wayland/Mir replacing X.
Originally Posted by scionicspectre
On the raspberry pi side, xbmc was ported to work with GL ES as Open Arena, it all depends on developers motivation to do it.
Last edited by TheOne; 04-09-2013 at 03:27 PM.
Seem reasonable to me. I guess quite a lot of ubuntu phone early users will be enthusiast that flash it on a android phone (even after the first actual ubuntu phones come out), and what easier way to support more phones than being able to use their android drivers.
I will at least keep an eye on ubuntu phone and sailfish, I want something more like maemo (that is, something a little bit more in line with linux desktops). I think there very well might be a small market made up by tech enthusiast for one of these, at least as 3d party roms for other androids.
Maemo on N900 refused 3D drivers b/c of the closed-source reason. Ubuntu made it big with great 3D on closed drivers before they became open, so I'd think the same will happen in mobile.
Since Mir (as opposed to SurfaceFlinger) provides C/C++ bindings to these 3D drivers, we can finally get the most out of ARM hardware.