View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#183
Originally Posted by Benson View Post
[*]The N9 (or whatever the first Meego device is -- I'll call it N9 here), by all (unconfirmed) leaked reports, is an OMAP3, and specifically an OMAP3640 -- essentially identical to the N900's OMAP3430, but with a process shrink and higher clocks. While this similarity doesn't necessarily make it legal to procure a copy of Nokia's Harmattan release for the N9, mash it up with the latest hackers-only N900 build, and come up with what amounts to a Harmattan-N900 build, I think it will make it technically straightforward, and going from there to legal will only require Nokia to make some closed components redistributable to owners of previous Nokia devices, not open-source or even globally re-distributable -- much easier to push through.[/list]
On a side note, this is a two edged sword. This means that there will not be a single OMAP3 'real' MeeGo device, which casts certain shadows on the N9's future. It could help A LOT if somebody official dropped in a future-proofing guarantee or two around release time. What I'm saying is that, from a MeeGo aspect, the N900 and the N9 aren't that much different, not only hardware, but software-wise, either. You will never be able to OTA the N9 to the next version of MeeGo, and, from what is known currently, has the same stance on drivers and closed components as Fremantle (if you can't wrap your head around this, think about it as Maemo 6 and it will be clearer), so I can already envision stskeeps doing an "N9 hardware adaptation project for MeeGo". This has to be handled from day 1 of the N9 - the Maemo missteps were bad, but given the N9's 'mainstream' goal, questions of this magnitude CANNOT be left to the community.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 2 Users Say Thank You to attila77 For This Useful Post: