to me, this article seems a summary, not a new technolog exploit.
Totally agree with the first comments, power is not a little concern. In fact, power vs. performance(features) always is a the toughesst headache.
Back to how to improve rich features of futuer mobile handsets, personaly thinking, it is not nesscceary to deploy so many functinalities at one machine, most of the users time is for basic communication purpose, not for entertainment. Too much effort attached to high-end market maybe exhaust itself without or with little reward
There are several parts to this article that have yet to appear. Yes, that is a problem and VEE has an impact. There have been articles on VEE on this site--both covering the announcement of the technology, and a contributed article from QuickLogic. I was very impressed with the technology when I first saw a demo at their facility. Thanks for writing--anyone else want to chime in?
This is a nicely thought through presentation of what it takes for a phone to be technically able to support video, but it neglects to address two things that will need to be changed before users embrace video.
The first of these is if you use your phone for video its back-light will run the battery down very quickly. I use a Samsung Instinct, which is not nearly as bad as the HTC Touch or Apple iPhone for some reason, but it still will drain a battery in no time.
Second is the current LCD screens are incapable of being viewed in direct sunlight even when backlight power is set at the highest level (faster battery drain).
I've looked at several emerging technologies that have been proposed to solve this problem and the only one I've come across that makes any sense at all is called VEE from QuickLogic.
Could you comment on the two problems noted above and, if you have the time, QuickLogic's VEE technology?
Blog Doing Math in FPGAs Tom Burke 18 comments For a recent project, I explored doing "real" (that is, non-integer) math on a Spartan 3 FPGA. FPGAs, by their nature, do integer math. That is, there's no floating-point ...