> > Most of those apps should be ok in 2.5 with normal timers - the select > > resolution is 1Khz in 2.5.x > > So, just to make _sure_ I've got this straight, does this mean that > usleep() will suddenly be 1ms-accurate, or do I need to do something > special? Also, is there some easy way to detect this accuracy? It does
