All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Rodrigo Rosenfeld Rosas <lbocseg@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RTDM timing problems
Date: Thu, 02 Feb 2006 17:26:51 +0100	[thread overview]
Message-ID: <43E232CB.7000700@domain.hid> (raw)
In-Reply-To: <200602021323.04666.lbocseg@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Rodrigo Rosenfeld Rosas wrote:
> Em Quinta 02 Fevereiro 2006 10:48, você escreveu:
> 
>> Rodrigo Rosenfeld Rosas wrote:
>>> Em Segunda 30 Janeiro 2006 16:42, Jan Kiszka escreveu:
>>>> The point is that rtdm_clock_read() relies on the nucleus timer being
>>>> started. Otherwise, it just returns plain wrong numbers.
>>>>
>>>> This makes me scream again for that damn timer being started
>>>> AUTOMATICALLY! I guess Philippe knows what I'm talking about... ;)
>>>> Meanwhile, we should state this in the docs. At least for 2.0.x, this
>>>> will remain true anyway.
>>> What can I do for now? What is the relation between the system time and
>>> the timer?
>> Just start the timer before using rtdm_clock_read().
> 
> Sorry, It is not clear to me how can I do that.

rt_timer_start() if you use the native API in your application. But I
would suggest to maintain a simple helper tool just for starting /
stopping the timer for native apps as long as this is explicitly needed.
As I indicated, plans exist to overcome this in 2.1.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

      reply	other threads:[~2006-02-02 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 18:11 [Xenomai-help] RTDM timing problems Rodrigo Rosenfeld Rosas
2006-01-30 18:42 ` Jan Kiszka
2006-01-30 23:17   ` Jeroen Van den Keybus
2006-01-31  9:46     ` Jan Kiszka
2006-02-02 12:46   ` Rodrigo Rosenfeld Rosas
2006-02-02 12:48     ` Jan Kiszka
2006-02-02 15:23       ` Rodrigo Rosenfeld Rosas
2006-02-02 16:26         ` Jan Kiszka [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E232CB.7000700@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=lbocseg@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.