Sleeping with CLOCK_REALTIME should use the WATCHDOG_ABSOLUTE
clock discipline for the threadq so that the timeout interval
may change in case the clock source changes. Similarly,
CLOCK_MONOTONIC uses the WATCHDOG_RELATIVE threadq that will
only wakeup the thread after the requested count of ticks
On Thu, Jul 14, 2016 at 9:04 AM, Pavel Pisa wrote:
> Hello Gedare,
>
> On Wednesday 13 of July 2016 19:39:45 Gedare Bloom wrote:
>> Gedare Bloom (5):
>> cpukit: Add and use Watchdog_Discipline.
>> posix: add clock_nanosleep and tests
>> cpukit/rtems: fix return type mismatch for _TOD_To_seco
It may be worth using a constant expression for the 512byte header
parameter, since this 512 reappears in a couple of math expressions,
if one ever changed it that would be a problem. Unless it is not
changeable / part of the tar "specification"
On Wed, Jul 13, 2016 at 7:59 AM, Alexander Krutwig
