jb0yx said:EDIT: found more info wonder how this matches up to the current pandora power consumption
http://news.softpedia.com/news/Intel-Pineview-Processor-Family-Detailed-113874.shtml
i realize 'fan-less' must be a huge step for intel (i can hear the champagne pops coming from intel's general direction), but call me when they get 'sink-less'....while the average power consumption will drop from 4W to 2W. The reduced power consumption is largely due to the redesign of Intel's platform, which has been reduced from a 3-chip setup to a 2-chip setup, with the memory controller and the graphics processor placed on the same die as the CPU. As a result, upcoming designs will implement a fan-less cooling solution, enabling a quieter computing experience.
on a different note, here's a brief follow-up on the zii, now that i've had some time to get to know it.
as i said, the device is a really interesting piece of hw. not yet consumer-ready (at least not in its non-android form), but interesting from a dev's POV nevertheless. regardless, i still cannot provide any solid benchmark numbers, and that's not because i don't want to. there's a serious obstacle to that, which obstacle may turn out permanent, or may be removed later, i'm not sure yet. i'm talking of a constantly-throttling power management (apparently trying to maximise the battery life); even in my rudimentary primer app, at one moment the fps may be 60, the next - 30, then it may jitter to sub-30, just to return to 60 a few moments later - as you understand, rather hard to measure anything under these conditions. on a positive note, though, the pesky throttling seems to be curbed when the device outputs to HDMI (yes, i can run my handheld code on my living-room TV in 720p - neat), so we'll see about that.
the platform's good sides:
* plaszma os is a rather accessible linux distro - throw in an sshd to it (nobody stops you from doing that) and voila - you're root on your own device - explore, tinker, fix.
* the proprietary SDK is really well designed for the most part (you can tell it comes from people with a huge background in media and graphics) - slim, yet functional. i wish it was more complete, too.
* with the newer fw revisions the device's features start to come to life one by one - now almost everything is functional, except for the bluetooth stack.
* the media-processor array in there is something that i, for one, belive, will be what future generations of handhelds will be orienting towards - i.e. no more specialized accelerators. or at least, not in today's configuration.
the bad sides:
* it appears the same future-looking tech in the zii is at the same time its achilles heel. judgeing by the overly-aggressive power-management, it seems that the device's power comes at a price, and the power draw is still not in its prime time. that's my guess, anyway; maybe i'm wrong, and it's all from the early stage of the product lifecycle (pre-market) - we'll see.
* no direct access to the media-processing array for now - that's the offical word from creative. if devs want something, creative will consider implementing the libs for that, but that's that. as you understand, that means no way to run custom code on the media array until GL ES 2.x comes to the device (not clear when, though signs point at a rather-sooner-than-later appearance), and maybe OCL in the long run (fingers crossed).
* the device has one of its two ARM cores and some 64MB (out of 256) dedicated currently to its 'core functions' - ie. the linux does not manage those, and neither do your apps. the positive aspect of that is that the media array does seem to be a totally autonomous engine from the POV of your code.
* no FPU on the ARM can be generally a hurdle, but so far the fp emulation has held up sufficient for most tasks, given one does not try to brute-force their way, but puts some thought in what they do.
all that said, i'm not seeing the zii as a pandora substitute, and i'm still looking toward the latter with the same enthusiasm i had on the day i ordered it.
Last edited by a moderator: