With our custom bsp of rtems (based on sparc/leon3 from 4.11.3) we are observing that rtems_task_wake_after() and usleep() quite often sleeps less than the requested amount when measured with rtems_clock_get_uptime_nanoseconds() timestamps.
Is this expected behaviour for sleep in rtems or is this indicative of some issue in our bsp (possibly in the realms of our clock driver, either affecting the actual sleep or the measurement, or both). The opengroup specification of usleep() indicates that it should always sleep equal to or more than the requested time, provided no signals: http://pubs.opengroup.org/onlinepubs/009695399/functions/usleep.htm -- Martin Erik Werner Software Engineer | ÅAC Microtec AB | Clyde Space Ltd. aacmicrotec.com/privacy-policy _______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
