So I thought I'd do some tests since I got my new
Beagleboard (thanks Thomas!). What is
this? well you can go follow the link - but it's an OMAP3530 based devel board
with pretty much nothing much on it other than the CPU. You need to plug in
serial to get the console - there is no input or screen on it... but it does
have DVI out and a usb OTG port (which so far has been utterly useless to me
as my supposed USB-A to USB-Mini-A doesn't work for OTG :( ). Anyway. This
little CPU (SoC - System on a Chip) is not too shabby. it's not even running
at the 600Mhz rated that the 3530 can do (mind you that's overdrive - but I'd
expect to use that normally as the other power case is 0 clock so while on
and doing things - do them fast, otherwise sleep as much as you can). Also
the RAM could be clocked up much higher (it's at 133Mhz on this board).
So that covers the hardware. Software wise I'm using expedite below. This is
the Software-X11 engine. Output is 16bpp RGB565 (except the Desktop which is
RGB32). The Desktop of course will have multiple threads rendering. It also
gets MMX and SSE assembly. The ARM systems get the plain C routines. So thus
far I have yet to put in any ASM for ARM in the software routines - but I
intend to throw in some preload (pld) calls as well... but... what I really
need to do is put in some NEON (OMAP3'x equivalent of MMX/SSE that actually
doesn't suck). I have NOT done any of this - so the below numbers are RAW
as-is. the PXA270 might have some room for optimising with Wireless MMX. The
s3x2442 I think is pretty much not going to go anywhere as it's ARMv4, so a
lost cause. So take the numbers for the PXA270 as "could be a little better".
From what I have read of the 3530's NEON - it could get a fair bit better if
not 50% or more on the FPS numbers below (yes the numbers are in frames per
second, rendering to a QVGA sized window in all cases).