Netweaver | # 41 | 2011-01-20, 20:49 | Report

the smoking gun ??? : Onkalo Samu.P (Nokia-MS/Tampere)
is the one responsible back in Sept. (at least back then) :
http://lkml.org/lkml/2010/9/3/58

Nvidia also seemed to be very involved with this magnetometer chip kernel driver source ...

buchanmilne | # 42 | 2011-01-20, 20:54 | Report

Of course Meego targets Intel platforms, otherwise, what would be the point of it not being Maemo6?

Of course there are Intel kernel adaptions, there is an Intel-based reference handset, as well as an arm-based Nokia reference handset (which many of us have).

Of course Intel would like to see commercial launches of Meego-powered handsets with Intel CPUs.

But, none of that necessarily has anything to do with what Meego handset Nokia will be launching (which will most likely be ARM-based).

Honestly, it seems people don't even apply logic and reasoning.

Now, the real question would be about a Nokia tablet-like device.

One also wonders if a architecture agnostic "binaries" aren't a good idea for a multi-architecture project, or will there be an Intel vs ARM dichotomy of (proprietary) apps and apps stores for Meego?

Creamy Goodness | # 43 | 2011-01-20, 21:09 | Report

nokia and intel have to get meego ready for the launch devices
they HAVE to add kernel patches and drivers
we CAN tell what the prototype devices include by looking at the source tree and testing results and bug reports.
it's possible these prototypes are not "final" but they are going to be pretty close by now. my logic and reasoning is better than yours

Netweaver | # 44 | 2011-01-20, 21:10 | Report

You're not referring to a cross-architecture, device agnostic 'language' based on a certain 'dalvik' I hope ?

Apart from that I think you're right. the physical dependency of the binary to the architecture is not good for the unity and uptake of Meego. Then again, proper procedures and a proper common build service (one or more OBSes) will prevent that as much as possible.

I saw discussions on the meego-dev list talking about this exact mixture of closed and open source binaries, for multiple architectures, in one build service. So they tried to do the proper thing

Netweaver | # 45 | 2011-01-20, 21:18 | Report

don't forget Maemo6/Harmattan is NOT Meego 1.2 or Meego 1.3. It will just be able to run the same software. Marketing wise it a "Meego instance". Deep down Nokia was too far ahead to wait till Meego was finally coming to age. So the N9 (whatever it's name will be) doesn't have to exist FULLY in the Meego kernel tree NOW.

But I do expect that Nokia is merging as much as possible of the current N9 product specifics already in, to get a proper unified kernel, maybe to include after launch in a PR.

Better to get rid of dual kernel code base as soon as possible, without killing off the already narrow timelines.

HellFlyer | # 46 | 2011-01-20, 21:19 | Report

Non taken since I know what you mean and feeding rumor mill is not what I was intented to do. Engadget's problem (just like a lot of other US tech "news" sites is that they twist and alter Nokia related news.
That beign said I think we will see an Atom based Nokia device (remember Nokia's netbook?) but not a phone!

Stskeeps | # 47 | 2011-01-20, 21:26 | Report

We're pretty much equally screwed/good (X86 and ARM) these days, comparable build times, similar issues, etc. There's always a bit of fun in porting.

I still maintain that people ought to see how "dangerous" (for competitors) it is when Nokia can practically merge together Nokia's MeeGo-based OS + MeeGo Core + a hardware adaptation, in very little time, to deploy on new types of devices, processors, form factors.

Example could be: Existing stack of Qt applications/Nokia differentation, make a MeeGo hardware adaptation for device, test, ship..

It makes R&D a lot easier having a portable platform.

bchliu | # 48 | 2011-01-20, 21:26 | Report

Thats where QT comes in.. Code portability.. between ARM S^3, ARM Maemo, ARM Meego and x86 Meego..

They'd have to be to remain competitive since everything else is going this direction. In fact, I'm willing to bet they will go one step further and come up with a QT JIT to standardise not just code - but binaries across the board as much as Android does the same way.

Even Microsoft is going this way with Windows 8 being announced for ARM. The market is moving in this direction for everything (even Apple has Rosetta Stone for universal binaries with x86/PPC for years now since they moved to x86).

Rauha | # 49 | 2011-01-20, 21:27 | Report

Dig into meego.com bug and mailing lists, and you'll find plenty of Nokia engineers located in various Nokia research centers in Finland doing stuff with Atom/Medfield . Curiously their testing and bug reporting has really ramped up since November.

That of course doesn't as us such mean that N9 will be Atom based.

retsaw | # 50 | 2011-01-20, 21:28 | Report

The x86 compatibility gives Intel quite a handicap here, maybe Intel can overcome it, but ARM currently has the advantage when it comes to low power CPUs.