Tristan
n00bie GP32 coder (MasterMind)
There are ofcourse pros and cons to this upgrade. The pros include the fact that if a program is already hugging the 166MHz line, even though it is very efficient (ASM), it might be able to run fullspeed at 180MHz. Ofcourse the cons are that a lot of people won't be able to run this new game properly.
My only response to this can be: "Though luck". Now this may seem a little harsh at first, until you hear that my GP32 can't overclock past 166MHz. If a developer wants to develop a game that runs at 180MHz, please god, let him.
The only games likely to need 180MHz are some goodlooking 3D games, or emu's. Now emu's are most likely already efficient with loads of ARM ASM cores floating around. For example, I know DJWillis' ScummVM is quite close to the 166MHz border with OGG support. Know we all know OGG takes up a lot of CPU power, so should DJWillis keep optimizing the OGG support and make it run at 166MHz, risking that he loses interest and drops the project or should he make an option to let it run at 180MHz? Your choice...
PS
DJWillis was used purely as an example, and has nothing to do with this topic.
My only response to this can be: "Though luck". Now this may seem a little harsh at first, until you hear that my GP32 can't overclock past 166MHz. If a developer wants to develop a game that runs at 180MHz, please god, let him.
The only games likely to need 180MHz are some goodlooking 3D games, or emu's. Now emu's are most likely already efficient with loads of ARM ASM cores floating around. For example, I know DJWillis' ScummVM is quite close to the 166MHz border with OGG support. Know we all know OGG takes up a lot of CPU power, so should DJWillis keep optimizing the OGG support and make it run at 166MHz, risking that he loses interest and drops the project or should he make an option to let it run at 180MHz? Your choice...
PS
DJWillis was used purely as an example, and has nothing to do with this topic.