the gp2x is not in the dreamcasts domain in terms of performance
[DC SPECS]
# CPU: SH-4 RISC CPU with 128 Bit FPU functions for 3D graphics computations (operating frequency: 200 MHz, 360 MIPS, 1.4 GFLOPS)
# Graphics Engine: PowerVR2 CLX2, 6.7 Mio polygons/second peak performance, supports Trilinear filtering
# Memory: Main RAM: 16 MB 64 Bit 100 MHz, Video RAM: 8 MB 4x16 Bit 100 Mhz, Sound RAM: 2 MB 16 Bit 66 MHz
# Sound Engine: Yamaha AICA Sound Processor: 22.5MHz 32-Bit ARM7 RISC CPU core, 64 channel PCM/ADPCM sampler, 128 step DSP
[GP2X SPECS]
# CPUs: Dual-core: 240 Mhz [4] host ARM920T + 240 Mhz ARM940T integrated into SoC - Overclockable by software (CPU cores rated at 200 MHz, but seem to operate at 240 MHz+ in all systems. Most machines' ARM920T can operate stably at 266 MHz, some at over 300 MHz.)
# Chipset: MagicEyes MMSP2 SoC (System-on-a-Chip)
DC has an 128bit+FPU processor gp2x has two 32bit processors
both are Reduced Instruction Set Computers
but then again gp2x 920T + 940T roughly at 440 mips
DC PPC SH-4 RISC 360 mips
[and then it gets real hairy]
DC has an PowerVR2 3d chip with 8mb vram
gp2x has an 2d accelerator that uses main memory
DC has 16mb main memory
Gp2x 64mb system wide
so my guess is that DC wins performance vise
but PSX emu is not out of reach for any of the systems
the winds could change if
1. somebody wrote a good kernel module that interfaced the 2 processors
2. GPH or open2x figures out a way to utilize the full 64mb with the linux kernel
this is my thoughts on the systems and should not be taken as "pure" facts but i think its a fair comparison
i have a question for zodttd do you build PSX4ALL binaries against Glibc or uclibc (wouldnt uclibc be better suited for an embedded system performance/size vise ?)
[DC SPECS]
# CPU: SH-4 RISC CPU with 128 Bit FPU functions for 3D graphics computations (operating frequency: 200 MHz, 360 MIPS, 1.4 GFLOPS)
# Graphics Engine: PowerVR2 CLX2, 6.7 Mio polygons/second peak performance, supports Trilinear filtering
# Memory: Main RAM: 16 MB 64 Bit 100 MHz, Video RAM: 8 MB 4x16 Bit 100 Mhz, Sound RAM: 2 MB 16 Bit 66 MHz
# Sound Engine: Yamaha AICA Sound Processor: 22.5MHz 32-Bit ARM7 RISC CPU core, 64 channel PCM/ADPCM sampler, 128 step DSP
[GP2X SPECS]
# CPUs: Dual-core: 240 Mhz [4] host ARM920T + 240 Mhz ARM940T integrated into SoC - Overclockable by software (CPU cores rated at 200 MHz, but seem to operate at 240 MHz+ in all systems. Most machines' ARM920T can operate stably at 266 MHz, some at over 300 MHz.)
# Chipset: MagicEyes MMSP2 SoC (System-on-a-Chip)
DC has an 128bit+FPU processor gp2x has two 32bit processors
both are Reduced Instruction Set Computers
but then again gp2x 920T + 940T roughly at 440 mips
DC PPC SH-4 RISC 360 mips
[and then it gets real hairy]
DC has an PowerVR2 3d chip with 8mb vram
gp2x has an 2d accelerator that uses main memory
DC has 16mb main memory
Gp2x 64mb system wide
so my guess is that DC wins performance vise
but PSX emu is not out of reach for any of the systems
the winds could change if
1. somebody wrote a good kernel module that interfaced the 2 processors
2. GPH or open2x figures out a way to utilize the full 64mb with the linux kernel
this is my thoughts on the systems and should not be taken as "pure" facts but i think its a fair comparison
i have a question for zodttd do you build PSX4ALL binaries against Glibc or uclibc (wouldnt uclibc be better suited for an embedded system performance/size vise ?)
