The clock values of CLOCK_MONOTONIC_RAW and CLOCK_MONOTONIC are not necessarily compa...
commit315ab7de4ba9da1ce17cbf5b5882a87895809f0e
authorjwoithe <jwoithe@2be59082-3212-0410-8809-b0798e1608f0>
Mon, 25 Jun 2012 14:37:30 +0000 (25 14:37 +0000)
committerjwoithe <jwoithe@2be59082-3212-0410-8809-b0798e1608f0>
Mon, 25 Jun 2012 14:37:30 +0000 (25 14:37 +0000)
treef19151aebce3c29f894432571e9f29fe571a3409
parentb2875aee31bcc60135b3966ea30580aa9aa763cc
The clock values of CLOCK_MONOTONIC_RAW and CLOCK_MONOTONIC are not necessarily comparable.  Since clock_nanosleep() can't be used with CLOCK_MONOTONIC_RAW - necessitating the use of CLOCK_MONOTONIC instead - this means it's not possible to use TIMER_ABSTIME with clock_nanosleep if CLOCK_MONOTONIC_RAW is the system clock source.  For simplicity, disable the use of TIMER_ABSTIME unconditionally when implementing SleepUsecAbsolute() at this stage.

git-svn-id: svn+ssh://ffado.org/ffado/trunk@2173 2be59082-3212-0410-8809-b0798e1608f0
libffado/src/libutil/SystemTimeSource.cpp