Dan East wrote:I can't comment on any 2300 specs at that level, nor can I compare it to some other chip. ATI played a dominate role in creating the OpenGL ES spec. They even drafted it in the first place. Imagination is clearly playing catch-up in this area, as they only announced at CES 2004 they would have OGLES support later this year, while the 2300 already has complete (and demonstrated) OGLES drivers in place.
Dan East
It is not my intention to question your knowledge in this area Dan, but according to the interview with the MBX development team, they are also part of the Khronos group:
"Seeing this is OpenGL though I assume you'll be able to utilise your own extensions there?
Absolutely, and that's exactly what we'll be doing so we'll have full support of the capabilities of MBX with OpenGL ES.
So in essence you'll have a superset of the core OpenGL ES?
Yes. We're heavily involved in the Khronos group and we're one of the twelve promoters of the technology."
http://www.beyond3d.com/interviews/pvrmbx/index.php?p=3
Also, Imagination has never shown any intention into forcing a 3D proprietary API for the PocketPC. It will use MGL (PowerVR's API that's used since the PVR Series 1) for operating sistems that do not have #native# support for OpenGL ES (linux and symbian). For pocketpc devices (which I think is the matter in question here) it will use exclusively D3D Mobile.
I can't say the same for ATi since they list a so-called "ATI Core Driver - hardware abstraction layer". (correct me if I'm wrong.. I only know what I see in the specs page..)
One thing I notice is that ATi doesn't mention the development of drivers for D3D Mobile anywhere.. Maybe they are claiming that the chip is compatible with the XScale architecture, but they are not intending to implement it for real (if they are only targeting cellphones with 16bit qvga lcds, it would explain the "up to 2Mb" spec).
I'm a big ATi fan. I've been using their desktop graphics cards for over 3 years and I can say I'm not disappointed at all.. But considering that MBX has been in development for nearly 4 years now, my guess is that they are taking a lead here (theoretical performance-wise, of course).
And maybe it's not correct to evaluate the current Xscales as being the bottlenecks for these chips since they aren't planned to come with any current XScale (at least not the PXA255/63).