Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 3 days, 18 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 4 days, 13 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 6 days, 22 hrs ago - more...
|
2011-01-20
, 20:54
|
|
Posts: 196 |
Thanked: 224 times |
Joined on Sep 2010
@ Africa
|
#42
|
Originally Posted by msnbcnnbcbs
Of course Meego targets Intel platforms, otherwise, what would be the point of it not being Maemo6?
kernel-adaptation-medfield.i586 2.6.35.3-9.1
xorg-x11-server-Xorg-setuid.i586 1.9.0-7.7
mesa-libGL.i586 7.9-2.28
glibc.i686 2.11.90-22.12
meegotouch-compositor.i586 0.8.0-1.22
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?
| The Following 4 Users Say Thank You to buchanmilne For This Useful Post: | ||
|
|
2011-01-20
, 21:09
|
|
Posts: 1,463 |
Thanked: 1,916 times |
Joined on Feb 2008
@ Edmonton, AB
|
#43
|
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
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
|
|
2011-01-20
, 21:10
|
|
Posts: 323 |
Thanked: 180 times |
Joined on Oct 2009
@ Gent, Belgium
|
#44
|
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?
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
|
|
2011-01-20
, 21:18
|
|
Posts: 323 |
Thanked: 180 times |
Joined on Oct 2009
@ Gent, Belgium
|
#45
|
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.
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.
 |
|
2011-01-20
, 21:19
|
|
Posts: 1,148 |
Thanked: 613 times |
Joined on Mar 2010
@ Toronto
|
#46
|
Originally Posted by NvyUs
Non taken
Why should I provide links to publicly available logs, they are no harder to find than that engadget article.
Spoon fed generation need to learn how to research for themselves instead of using RSS feeds to the latest tech site blog rumours.
no offence intended
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!
__________________
The quieter you become the more you are able to hear
"I'm a N900 user, can I haz Flash 10 plz?!11!?"
© Jaffa
Elopocalypse started on 11.02.2011
The quieter you become the more you are able to hear
"I'm a N900 user, can I haz Flash 10 plz?!11!?"
© JaffaElopocalypse started on 11.02.2011
 |
|
2011-01-20
, 21:26
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#47
|
Originally Posted by cfh11
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.
Not true - they have been working on x86 from the start (see Aava Mobile). If true, I would not be surprised as the x86 handset build seems to be a lot further along than the ARM version. I remember Stskeeps saying a while back that for whatever reason they have encountered all kinds of problems that the x86 team has not.
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.
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
|
|
2011-01-20
, 21:26
|
|
Posts: 158 |
Thanked: 61 times |
Joined on May 2010
|
#48
|
Originally Posted by buchanmilne
Thats where QT comes in..
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?
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).
|
|
2011-01-20
, 21:27
|
|
Posts: 1,400 |
Thanked: 3,751 times |
Joined on Sep 2009
@ Arctic cold of northern .fi
|
#49
|
Originally Posted by Netweaver
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.
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 ...
That of course doesn't as us such mean that N9 will be Atom based.
|
|
2011-01-20
, 21:28
|
|
Posts: 701 |
Thanked: 585 times |
Joined on Sep 2010
@ London, England
|
#50
|
Originally Posted by Creamy Goodness
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.
http://www.anandtech.com/show/3696/i...e-processor/16
there's no reason not to believe intel can't beat ARM in performance and power savings, they have the best technology and most R&D money. Just worry about MeeGo and hope Intel & Nokia know what they're doing with the hardware.
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 ...