
Originally Posted by
curaga
I recall my E-350 built mesa in about ~15min. Translating that to an older single core atom, maybe 5 days

LOL! Sounds about right though
. After compilation hung there at "running /usr/bin/makedepend" for like half an hour, I terminated it. Didn't bother to investigate what went wrong, if something really hung or if the processor was just taking it's sweet time. I now compiled on a laptop, Pentium-M 1.73GHz, took a bit more than 15 minutes.
Before:
Code:
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 8.0.3
After:
Code:
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on i915 (chipset: 945GME)
OpenGL version string: 2.1 Mesa 8.1-devel
OpenGL shading language version string: 1.20
To see if it works, I started EDuke32 with the Polymost HRP, launched a game and just stood there. Classic driver 48-49fps, gallium driver 44-45fps. So the gallium driver is indeed a bit slower. Of course what I'm doing here is not a proper test, but it's something.
Next step, Need for Speed 4 in wine. Didn't even start with the gallium driver, just threw an error. So I guess I'll be sticking with the classic driver, no matter how cool "OpenGL version string: 2.1" looks 
ZootNerper: You have a CedarView machine with PowerVR graphics, while what's being tested here is Diamondville, with Intel graphics. Your issues have nothing to do with the Atom processor, it's all about graphics. And the next architecture, ValleyView, won't have PowerVR graphics anymore.