I actually just finished a pacman -Syyu (Took a while, I had an older archlinux distro) and it seems to have a new kernel configured with CONFIG_HIGH_RES_TIMERS=y as you mention, so my 1ms nanosleep now looks to be giving my cpu a break, while maintaining several hundred simulation loops / second. T...

Like nanosleep(), usleep() guarantees it won't return before its specified duration, but makes no promises about how soon after it will return. Unfortunately it behaves with the same 10ms resolution.

Perhaps take a look at clock_gettime.

http://linux.die.net/man/3/clock_gettime

I've recently received my Pi, and I've begun working on a test c++ OpenGL ES program. I have a thread for simulation updates, however my current options are to have it run at full speed 50,000+ times/sec, pushing system load to 100%, or to use nanosleep() which seems to only implement down to 10ms, ...

I brought my newly arrived Pi into work this morning to try it over lunch, and had the same problem. Read a few posts on here about it, and was going to wait until I got home this evening to try my hand at resoldering x1, but decided on a whim to just *lightly* flick x1 a few times, and so far seems...