Moblin/MeeGo: The Fastest Smartphone OS?

PC game developers often criticize Intel for holding back the whole industry by not shipping faster integrated graphics. Game developers have to target the least common denominator of graphics hardware, which happens to be Intel’s integrated graphics. So nearly all PC games suffer as a result.

Moorestown is a good bit faster than any ARM based SoC on the market today. Memory bandwidth limitations aside, if you look at our recent Apple A4 vs. Atom performance comparison you’ll see what sort of gap exists between what you get today in a smartphone and what Intel is trying to deliver:

Unfortunately for Intel, all smartphone OSes are optimized for the least common denominator in SoC performance. That is 400MHz - 1GHz ARM11 or Cortex A8 class hardware. Smartphone OS vendors need to make sure their OSes run on the majority of hardware, which just isn’t Moorestown. Intel needs something to take advantage of its added performance, so Intel had to go off and do some software work. Irony is hilarious.

Moorestown is useless if it doesn’t offer significantly better performance or user experience (or both) than its competitors. To ensure this, Intel did two things.

First, Intel bought a company called Wind River. A $400M company prior to acquisition, Intel snagged WindRiver back in July of 2009. Their mission statement? To take open source software and make it commercially viable.

Whether it’s stress testing or adding new features, Wind River takes open source software and improves it to the point where you can now sell it as a commercial product. This is similar to what Apple did with the base of much of OS X. You take some good open source projects and pay people to polish and harden the last 10 - 20% of them.

Wind River has a platform for Android. It incorporates Atom optimizations into Android, hardens the software stack and prepares it for use in Moorestown devices. Google has little incentive to dedicate a lot of support to Moorestown, so Intel had to internalize that.

The second thing Intel did to ensure Moorestown’s performance wouldn’t go to waste was the development of Moblin. A smartphone/tablet targeted Linux based OS, Moblin has been lurking in our minds for well over a year now. I never really got why Intel felt the need to support the development of a mobile OS until now.


Moblin running on Moorestown

Moblin will be the highest performance OS for Moorestown to run on top of. Until a company like Apple or Google decides to embrace Moorestown, Intel needed a way to guarantee an optimized software stack for Moorestown. Moblin is that guarantee. It’s designed from the ground up to be Atom optimized, it’ll be faster than any other OS running on Moorestown and will also do the best integration of power management for Moorestown. Intel knows the architectures of its chips best, and Moblin effectively knows whatever Intel knows.

A Moorestown specific OS could also evolve to include more CPU intensive UIs and features just wouldn’t work well on the majority of ARM devices out there, which would in turn give Moorestown a tangible feature advantage in the smartphone market.

Earlier this year Intel and Nokia announced their cooperative efforts on an OS called MeeGo. Take one part Moblin and one part Maemo and you get MeeGo. The idea is to take Moblin and expand it to more platforms (particularly ARM based devices). Moblin will eventually go away and there will only be MeeGo, however there are currently smartphones and tablets based on both Moblin and MeeGo in development.

While Moblin and MeeGo are the best platforms for Moorestown, there’s a lot of reinventing the wheel that needs to be done. Thus the first Moorestown based smartphones will likely run Android.

The Neutral Role

Carriers aren’t very happy with Apple and Google. They’ve effectively wrestled power away from the carriers and left them as nothing but network providers. In my eyes this isn’t a bad thing. Over the past several years the major carriers have shown us nothing other than they can’t be trusted with too much power. Where there is frustration, there’s money to be made.

Intel wants to capitalize on that frustration by offering the carriers an alternative. Moblin won’t be branded, carriers could customize their own builds and do whatever they want with them. The carriers would ultimately limit what could run on their phones, much like Apple does today. It puts power back in the hands of the carrier, which is something they obviously like.

Whether or not that’s a good thing for the consumer is another question entirely. Intel tells me that the carriers have learned a lot from watching Apple and Google, and that they have no interest in making the same mistakes twice. I’m not sure I believe that just yet.

More OS Support if Needed

Intel made it clear that while it’s only focusing on Android, Moblin and MeeGo at the start, if a vendor were to express interest in doing a custom design around Moorestown the answer wouldn’t be no. In other words, if Apple wanted to move iPhone OS to Moorestown, Intel will make it happen.

Intel also mentioned that Moblin is an enabling necessity for Moorestown. If that need ever goes away, it has no issues handing the market over to Apple, Google or whoever wants to carry the torch. Intel doesn’t want to be in the mobile OS business, it’s simply participating because it is compelled to in order to build the best environment for Moorestown to succeed. If Intel’s plan works out, then all smartphones would eventually use some Moorestown derivative and they would be optimized for much higher performance CPU right off the bat. We’re not there today, so Moblin has a role to play.

There's also the question of Windows 7 support. Without a PCI bus, Moorestown can't run the popular desktop OS. However if Intel were to deliver a version of Moorestown with PCI support, that could solve that problem...

Aava to the Rescue: An iPhone Sized Moorestown Platform Intel Takes a Stand: No Windows Phone 7 Support
Comments Locked

67 Comments

View All Comments

  • CSMR - Wednesday, May 5, 2010 - link

    Agreed. Intel needs a process advantage to beat ARM with x86. (Notwithstanding the software pain of transitioning to x86). But it actually doesn't have it. They are roughly on par in this segment, Intel leading by maybe a few months.
    http://channel.hexus.net/content/item.php?item=225...
  • hyvonen - Wednesday, May 5, 2010 - link

    Sorry, but Intel is ahead way more than two months. Intel's 32nm process is better from performance/power point of view than 28nm bulk processes from others. Relying on numbers such as 32nm and 28nm to figure out which one is better is like using only CPU clock frequency numbers to determine which CPU is fastest.

    Oh, and since Intel's 32nm products started shipping in the beginning of this year, Intel is roughly a year ahead... maybe more.
  • metafor - Wednesday, May 5, 2010 - link

    Yes and no. The 32nm shipping is the high-performance (high leakage) one used in desktop/laptop processors and also the current Atom. For a smartphone, that simply won't do.

    The 45nm low-leakage process they used for Moorestown is new territory for Intel and in that respect, they are behind TSMC. While the current bulk silicon 45nm isn't faster than Intel's metal gate 45nm, it's a lot less leaky in terms of power. I would guess it'll take Intel 2 iterations or so before they have leakage down to the point of being competitive. But they have performance going for them.
  • hyvonen - Wednesday, May 5, 2010 - link

    Yeah; first iteration: 45nm low-power process. Second iteration: 32nm low-power process.

    TSMC is stuck, and won't be able to come up with a low-power process beyond the current one for a couple of years. 40nm is in trouble, 32nm is toast. Good luck with making anything below 32nm "low power" in any sense of the word.
  • LuxZg - Wednesday, May 5, 2010 - link

    Ok, so this should be x86 CPU. So will the "tablet version" support normal Windows 7 OS or something similar? That's my only question.. I don't expect Win 7 on smartphone, but unless we have 100% software compatibility "x86 everywhere" won't mean much to people (except to Intel).
  • iwodo - Wednesday, May 5, 2010 - link

    It looks great, If Intel could give Apple some VERY good deal i guess Apple might take it.

    I cant wait for the 32nm Medfield.

    But Apple using it would means no more surprise in terms of Hardware.....
  • iwodo - Wednesday, May 5, 2010 - link

    After reading, I still do not understand the idea why Apple needs to buy other Chip Maker. If Morrestown is this good, and Medfield is much better. ( Apple should know it well before hand ) why spend money.

    Intel is making chips at volume much cheaper then Apple designing and making their own. Hardware CPU dont differentiate the product. Outlook and Software does.
  • WaltFrench - Sunday, May 9, 2010 - link

    “…I still do not understand the idea why Apple needs to buy other Chip Maker. If Morrestown is this good, and Medfield is much better.”

    I think you answered your own question. Apple, who probably had some inkling of Intel's plans, has been plowing ahead with proprietary silicon. They must think that for the next couple of years, anyway, they're better off with ARM-based designs, tweaked in-house and sent to whatever foundry gives them the capability they need.

    Can anybody estimate the number of Atom-class chips Intel sells? The general estimates are that ARM designs go into a billion devices per year, and Apple is probably thinking that they'll move 50 or 100 million per year. Intel would appear to have a serious resource/investment challenge, in addition to the business challenge of talking people into abandoning ARM.
  • Visual - Wednesday, May 5, 2010 - link

    Let me see if I get this straight... this is a x86 system. And it will NOT run standard x86 OSes or binaries?
    If so, the developers of this are complete idiots.

    It must definitely have the ability to run normal desktop windows apps at launch - either by running a full windows OS, maybe modded to make better use of small screen and no kbd, or at least by some wine-like layer. It must run dosbox with the dynamic core.

    Else it being x86 is completely useless.
  • safcman84 - Wednesday, May 5, 2010 - link

    Windows 7 for Phones is hardly an established Smartphone OS. As this chip is targeted for Smartphones, then not having support for Windows is not an issue.

    Besides, why would Intel support a OS that is not optimised for their CPU when it is touted as the most powerful smartphone solution ? A non-optimised OS will make the chip look bad. If Intel supports andriod devices (plus MeeGo and Moblin) suddenly get 2x the performance, with excellent battery life then Intel's decision not to support Windows based phones could force MS to optimise their OS for use on Moorestown, otherwise Windows based devices dont have a chance.
    Intel have not said they will NEVER support windows devices, just that they dont at the moment cos the current iteration of Windows 7 for phones is unoptimised.

    In addition, as someone who used Smartphone for use with work, I would happily deal with the inconvenience of having a slightly longer phone if I got 2x the performance for the same battery life.

    If the theoretical performance proves true in practice then:

    Andriod + Moorestown = Yes please

Log in

Don't have an account? Sign up now