On Wed, 2007-08-29 at 17:28 +0200, Jan Kiszka wrote:
Philippe Gerum wrote:
On Wed, 2007-08-29 at 16:32 +0200, Jan Kiszka wrote:
Markus Osterried (BA/EDD) wrote:
Hi,
it seems that in the RTDM API, all the timeout functions which use
nanosecs_rel_t have a strange behaviour.
The
Hi,
it seems that in the RTDM API, all the timeout functions which use
nanosecs_rel_t have a strange behaviour.
The timeout in nanoseconds is converted to ticks and the number of ticks
is rounded down. So when we want to wait e.g. 50 nanoseconds and the
timertick is 1 ms, xnpod_ns2ticks()
Markus Osterried (BA/EDD) wrote:
Hi,
it seems that in the RTDM API, all the timeout functions which use
nanosecs_rel_t have a strange behaviour.
The timeout in nanoseconds is converted to ticks and the number of ticks
is rounded down. So when we want to wait e.g. 50 nanoseconds and the
On 8/29/07, Philippe Gerum [EMAIL PROTECTED] wrote:
On Wed, 2007-08-29 at 16:32 +0200, Jan Kiszka wrote:
Markus Osterried (BA/EDD) wrote:
Hi,
it seems that in the RTDM API, all the timeout functions which use
nanosecs_rel_t have a strange behaviour.
The timeout in nanoseconds is
On Wed, 2007-08-29 at 16:32 +0200, Jan Kiszka wrote:
Markus Osterried (BA/EDD) wrote:
Hi,
it seems that in the RTDM API, all the timeout functions which use
nanosecs_rel_t have a strange behaviour.
The timeout in nanoseconds is converted to ticks and the number of ticks
is rounded
Philippe Gerum wrote:
On Wed, 2007-08-29 at 16:32 +0200, Jan Kiszka wrote:
Markus Osterried (BA/EDD) wrote:
Hi,
it seems that in the RTDM API, all the timeout functions which use
nanosecs_rel_t have a strange behaviour.
The timeout in nanoseconds is converted to ticks and the number of
