Rumor: N9 to have 1.2Ghz Atom - Page 6 - maemo.org

Active Topics

The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 3 days, 17 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...

Page 6 of 15

Thread Tools

Netweaver	2011-01-20 , 21:35
Posts: 323 \| Thanked: 180 times \| Joined on Oct 2009 @ Gent, Belgium	#51

nCDK is certainly an intel Medfield based handset, as per details in this bug report :

http://bugreports.qt.nokia.com/browse/QTBUG-15789

Quote & Reply |

mikecomputing	2011-01-20 , 21:39
Posts: 3,464 \| Thanked: 5,107 times \| Joined on Feb 2010 @ Gothenburg in Sweden	#52

Originally Posted by Netweaver

nCDK is certainly an intel Medfield based handset, as per details in this bug report :

http://bugreports.qt.nokia.com/browse/QTBUG-15789

THAT we already know

see qa report. But more intresting is if its N9 :-P

Quote & Reply |

	mrojas	2011-01-20 , 21:50
	Posts: 733 \| Thanked: 991 times \| Joined on Dec 2008	#53

Anyone remembers this?

I bet that the first MeeGo tablet will run in x86. It will make sense, since the form factor allows a bigger battery, and Intel seems to have been testing some MeeGo UI for tablets already (http://mynokiablog.com/2010/06/01/new-meego-tablet-ui/).

Every piece of know-how they get through this tablet can then easily go towards a x86 phone (if they eventually decide to make one); which could arrive in H2 2011 (fitting the schedules mentioned before).

If the N9 is going to be launched anytime soon; then the hardware should be decided already and getting ready to be mass produced.

(Credits to MyNokiaBlog for the picture)

__________________
Hola! Soy un Guía de Maemo!.

Vínculos interesantes si nos visitas por primera vez (en inglés): New members say hello , New users start here, Community subforum, Beginners' wiki page, Maemo5 101, Frequently Asked Questions (FAQ)

Si te puedo ayudar con cualquier otra cosa, sólo dilo!

Quote & Reply |

The Following 5 Users Say Thank You to mrojas For This Useful Post:
c0rt3x, cjp, kevloral, Netweaver, NvyUs

	kingoddball	2011-01-20 , 21:54
	Posts: 1,187 \| Thanked: 816 times \| Joined on Apr 2010 @ Australia	#54

Lies.......

__________________
The thanks button? Sure! You can press it!

I would!

Quote & Reply |

Creamy Goodness	2011-01-20 , 22:08
Posts: 1,463 \| Thanked: 1,916 times \| Joined on Feb 2008 @ Edmonton, AB	#55

ncdk is a handest. its at the link i posted earlier running handest tests and getting bug reports to do with calls and SMS. they have 3 revisions listed (EB1 EB2 EB3). It has to be close to final by now. I even gave you the screen size and keyboard and sensor info, and still you want to argue it's "something else".
I give up.

Quote & Reply |

	mrojas	2011-01-20 , 22:17
	Posts: 733 \| Thanked: 991 times \| Joined on Dec 2008	#56

Originally Posted by Creamy Goodness

ncdk is a handest. its at the link i posted earlier running handest tests and getting bug reports to do with calls and SMS. they have 3 revisions listed (EB1 EB2 EB3). It has to be close to final by now. I even gave you the screen size and keyboard and sensor info, and still you want to argue it's "something else".
I give up.

The "final" in "close to final" can get very long. There is a reason why calls and SMS get debugged first; it's because they give the biggest revenue to carriers, so they can't fail, ever. Even considering that the handset have been thoroughly debugged; they still need to do live tests, durability, factories, marketing, etc etc

All that can easily take months. That's why I believe the N9, based on ARM will be launched in Q3 2011, followed by an x86 tablet with voice capabilities in mid 2011, and a new x86 phone for Q3 2011.

What delayed them? Getting Qt and UX's unified correctly so customers and developers can transition between devices with minimum hassle.

Pure speculation on my part, btw.

Quote & Reply |

mikecomputing	2011-01-20 , 22:23
Posts: 3,464 \| Thanked: 5,107 times \| Joined on Feb 2010 @ Gothenburg in Sweden	#57

Originally Posted by bchliu

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.

QML is the answer to JIT

Quote & Reply |

Netweaver	2011-01-20 , 22:30
Posts: 323 \| Thanked: 180 times \| Joined on Oct 2009 @ Gent, Belgium	#58

the nCDK runs at stock (max.) speed at 1.6 Ghz.
Source : http://bugs.meego.com/show_bug.cgi?id=12418

Look in the 2nd attachment, the powertop log. :

Your CPU supports the following C-states : C1 C2 C4
Your BIOS reports the following C-states : C1 C2 C4
Cn Avg residency
C0 (cpu running) ( 0.0%)
polling 1.0ms ( 0.0%)
C1 mwait 0.1ms ( 0.1%)
C2 mwait 0.7ms ( 2.1%)
C4 mwait 7.5ms (103.6%)
P-states (frequencies)
1.60 Ghz 5.4%
1300 Mhz 0.2%
1100 Mhz 11.8%
900 Mhz 0.0%
600 Mhz 82.6%

Also, in the same log, plenty of technical drivers / chipnames, ready for translation in proper specs, some copied below:

[QUOTE]100.0% i2c:lis3lv02d
0.0% i2c:i2c_ledflash
0.0% 00:04.2 SD Host controller: Intel Corporation Device 0822
0.0% 00:04.1 SD Host controller: Intel Corporation Device 0821
0.0% 00:04.0 SD Host controller: Intel Corporation Device 0820
0.

0% 00:03.4 Communication controller: Intel Corporation Device 0819
0.0% 00:03.3 Communication controller: Intel Corporation Device 0818
0.0% 00:03.2 Communication controller: Intel Corporation Device 0817
0.0% 00:03.1 Communication controller: Intel Corporation Device 0816
0.0% 00:02.7 System peripheral: Intel Corporation Device 0832
0.0% 00:02.6 System peripheral: Intel Corporation Device 0830
0.0% 00:02.5 System peripheral: Intel Corporation Device 0827
0.0% 00:02.3 USB Controller: Intel Corporation Device 0829
0.0% 00:02.0 VGA compatible controller: Intel Corporation Device 0130
0.0% 00:01.4 System peripheral: Intel Corporation Device 0825
0.0% 00:01.3 Multimedia audio controller: Intel Corporation Device 082f
0.0% 00:01.1 SD Host controller: Intel Corporation Device 0824
0.0% 00:01.0 SD Host controller: Intel Corporation Device 0823
0.0% 00:00.5 Communication controller: Intel Corporation Device 082e
0.0% 00:00.4 Communication controller: Intel Corporation Device 082d
0.0% 00:00.3 Communication controller: Intel Corporation Device 082c

Devices without runtime PM
i2c:i2c_TC35894-nEB1
i2c:ak8975

i2c:i2c_cam2_img_sen
i2c:LW45-motor
i2c:LW45-sensor

i2c:i2c_msic_hdmi

i2cn544

i2c:ECI-nEB1
i2c:Sil9234-nEB1
i2c:i2c_fm
i2c:bcm4751-gps

i2c:bh1770glc
i2c:lp5523
i2c:mXT224

I'm sure there're still plenty of goodies to find in other bug details

Quote & Reply |

The Following 5 Users Say Thank You to Netweaver For This Useful Post:
c0rt3x, Creamy Goodness, pelago, pillar, Rauha

Creamy Goodness	2011-01-20 , 22:33
Posts: 1,463 \| Thanked: 1,916 times \| Joined on Feb 2008 @ Edmonton, AB	#59

Originally Posted by mrojas

The "final" in "close to final" can get very long. There is a reason why calls and SMS get debugged first; it's because they give the biggest revenue to carriers, so they can't fail, ever. Even considering that the handset have been thoroughly debugged; they still need to do live tests, durability, factories, marketing, etc etc

All that can easily take months. That's why I believe the N9, based on ARM will be launched in Q3 2011, followed by an x86 tablet with voice capabilities in mid 2011, and a new x86 phone for Q3 2011.

What delayed them? Getting Qt and UX's unified correctly so customers and developers can transition between devices with minimum hassle.

Pure speculation on my part, btw.

I see, so you think that Nokia, that will barely admit to the importance of MeeGo, actually is developing two MeeGo phones... And also is so insane they decided to skip making prototypes and testing of the N9, and will just test the n900 and this intel phone. Because that is exactly what you are implying when you say that this is not the N9 prototype...