there are more than one thing that dual core ARM doing better than single core.
* 1080p encoding and decoding without consuming all the cpu cycles
Task for the DSP (encoding) and GPU (decoding).
Originally Posted by
* Multitasking will be smooth and less time to do tasks
Possibly. However, is the CPU the bottleneck? In most cases my N900 is slow, it is due to IO wait, not actual CPU utilisation.
Originally Posted by
* gaming will be on a different level
Mostly a task for GPU
Originally Posted by
* smoother GUI transitions
Task for GPU
Originally Posted by
* better batter usage (in theory, two horses can climb steeper hill than one horse)
But, two horses need twice the food and water than one.
Originally Posted by
DSLR has the optical capability but mbile is fixed lense.
It's not only the lens optics, the sensor size has a huge impact on SNR.
Originally Posted by
Comparing Qualcomm to Cortex is like AMD to Intel.
No, it's like comparing AMD to x86. One is a subset of the other. Maybe you mean Qualcomm Snapdragon to TI OMAP?
Originally Posted by
if N9 doesn't have atleast dual core A9 + 1GB RAM then I don't think Nokia will ever compete in the fast growing mobile era.
A single-core, with higher clock speed then N900, with 512MB or 768MB would probably be enough, depending on the GPU (see some of the tweets about polygon rendering speed of N9, it is comparable to lower-end gaming devices). I doubt many users will see benefit of 1GB over 768MB on a mobile phone.
Originally Posted by
Also having 12MP camera is a bonus when recording video in high resolution and densing the pixel to 1080p is better than 5mp, eg. N8 took great videos quality.
If you want good video for least cost, a lower resolution sensor with less noise would result in less image processing overhead (but, this should be done by the DSP in most cases, not the CPU).
which would you prefer? An underpower device or an overpower device when it release? I bet your argument would change and your jaw would drop when you see a device that running MeeGo which has far more future proof hardware. Future OS upgrade will not be a set back.
That's what those people back in the old day since the first computer were built predicting that you won't use more than 1KB in the future. And guess what? a few years later they were wrong, even 1MB wasn't enough for simple user.
Don't predict the present with the future.
Better to have more than having insufficient, when you needing it you'd have enough to tap into for more RAM and CPU power. That goes with the GPU as well, in computer world there is no such thing is too much RAM and too fast cpu or storage. If we have that much we will use that much. Potentials and more potentials.
which would you prefer? An underpower device or an overpower device when it release? I bet your argument would change and your jaw would drop when you see a device that running MeeGo which has far more future proof hardware. Future OS upgrade will not be a set back.
That's what those people back in the old day since the first computer were built predicting that you won't use more than 1KB in the future. And guess what? a few years later they were wrong, even 1MB wasn't enough for simple user.
Don't predict the present with the future.
Better to have more than having insufficient, when you needing it you'd have enough to tap into for more RAM and CPU power. That goes with the GPU as well, in computer world there is no such thing is too much RAM and too fast cpu or storage. If we have that much we will use that much. Potentials and more potentials.
Those 640KB machines were tethered to a relatively unlimited power source.
IF having a quadcore beast means you'll have to lug a car battery in your backpack to survive a day, or recharge your phone (for 30 mins?) every 3 hour, then that gives a different meaning to a portable hardware.
We don't know that yet, that's what most people here seem to be concerned about.
Those 640KB machines were tethered to a relatively unlimited power source.
IF having a quadcore beast means you'll have to lug a car battery in your backpack to survive a day, or recharge your phone (for 30 mins?) every 3 hour, then that gives a different meaning to a portable hardware.
We don't know that yet, that's what most people here seem to be concerned about.
Isn't it was the same as when the N900 was introduce with the 5800 battery? People have their doubts and predictions of N900 as a blood sucking vampire that won't last a day with that much power in it.
Yeah I know but have you seen Tegra2? It's doing pretty good at maintaining the power management. I am sure that it will improve to fit in portable devices and last longer than N900 would Can't really question the technology. It's moving too quick and it will be substainable with a new type of battery that last longer and hold more charge than Li-iron.
@maxx: If there is one computer subsystem that is most stagnant; one that develops (in capacity and performance) the least compared all other subsystems, that would be the battery.
It'd be nice if you understand the context of other's arguments.
Harmattan is not dead yet, at least not on everyones machine, it seems Thiago Macleira (a very well positioned and knowledgeable Qt guru/designer) is still using a product called Harmattan.
Wouldn't he be using the real Meego in case the Harmattan/meego was cancelled : (just arrived on the meego-dev mailing list, about NEON (ARM specific) high performant version of memcopy)
Originally Posted by
Em terça-feira, 25 de janeiro de 2011, às 09:04:04, leonid.moiseichuk@nokia.com escreveu:
> We have tested version in our libc and Juha could share it.
Having looked at the disassembly of that function from my Harmattan sysroot, I am not sure it's the best.
It does the same thing that glibc tries to do: move as much data as possible on each step. That's great, except for when you have small memory chunks you want moved. My performance timings on real applications show that the overhead of selecting the best code path is worse than the benefit of the faster memory moving.