Gorillazero: you've done the 32MB mod? woohoo! You're the first, congratulations.

Did you send me an e-mail about it? I've done a OS reinstall and lost lots of e-mail, sorry about that. But if you've done the 32MB mod, surely the OC mod is a walk in the park!?
jlebrech and trooper: woah back there boys! So much misinformation...
First off, RAM access bandwidth is a problem in
every modern computer system, not just the GP32. That's why systems all have cache, to try and smooth out the load on the RAM bus. Believe me, if you try to do memory-to-memory copies on a 3GHz Pentium, even with the latest 500MHz DDR RAM, you'll get processor stalls while the memory catches up.
The GP32 doesn't run the memory at 133MHz, it runs at half (or quarter) of the CPU speed. So even at 166MHz, the RAM runs at 83MHz. That's not a problem for the RAM in
any GP32, because even when the GP32 was a new product, 100MHz RAM was the standard (my GP32, and most I would imagine, had 133MHz RAM). The problem is with the CPU, and its buffers on the memory bus which aren't specified to run above 66MHz (you can read that in the data sheet). I won't go into the details, but this is the reason that doing my mod to increase the CPU core voltage allows better overclocking.
Finally, the "ugly bug" is also with the CPU. When the CPU write-back cache gets full, and it has to be cleared, the memory access can prevent other functions (such as sound DMA) from working. That's why you get choppy sound when doing screen blits etc. So Samsung is to blame for it, but don't be too hard on them- when you have lots of data going around various sources and destinations, it's a very difficult problem to make sure that all the priorities are correct. If you get into the details of it, the memory bus architecture on any modern processor system is extremely complex.
Right, end of rant
