All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: matthieu.connaulte_xenomai@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] xenomai scheduler's ticks period
Date: Mon, 07 Jul 2008 16:16:36 +0200	[thread overview]
Message-ID: <48722544.7090203@domain.hid> (raw)
In-Reply-To: <5c3287e115e89c7cbb7c53402762cb2c@domain.hid>

Matthieu wrote:
> 
> On Mon, 07 Jul 2008 15:55:33 +0200, Philippe Gerum <rpm@xenomai.org> wrote:
>> Matthieu wrote:
>>>>> I need a clock to get the time with a 10 µs precision. I tought using
>>>> this
>>>>> master timebase, as it gives me a time in nanoseconds, irrespective of
>>>>> vxworks timebase.
>>>> That will work. The master timebase is always active and does return
>>>> nanoseconds
>>>> when inquired.
>>> What instruction I use to get this time ?
>>> I tried :
>>>
>>> #include <native/timer.h>
>> #include <nucleus/timebase.h>, but that's not the point.
>>
>>> xntbase_get_time(&nktbase);
>>>
>>> But it doesn't work
>> It ought to work, otherwise nothing would. What's the issue? Unpected
>> result?
> 
> I want to get the actual time at a 10µs precision. I will truncate the
> result as the master timebase is a nanosecond precision time.
>

xntbase_get_time(&nktbase) will get you that value. Really. What does not work
for you?

>> --
>> Philippe.
> 
> Matthieu
> 
> 
> 


-- 
Philippe.


  parent reply	other threads:[~2008-07-07 14:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4861045E.4010106@domain.hid>
     [not found] ` <14a573dd7f3ed8e10e00a083480c4622@domain.hid>
2008-06-24 16:40   ` [Xenomai-help] xenomai scheduler's ticks period Gilles Chanteperdrix
2008-06-24 17:10     ` Matthieu
2008-06-25  8:06       ` Matthieu
2008-06-26  8:07       ` Matthieu
2008-06-30  7:40         ` Matthieu
2008-07-01  8:28           ` Matthieu
2008-07-07  5:49             ` Matthieu
2008-07-07  7:49               ` Philippe Gerum
2008-07-07  9:49                 ` Matthieu
2008-07-07 11:45                   ` Philippe Gerum
2008-07-07 13:19                     ` Matthieu
2008-07-07 13:33                       ` Philippe Gerum
2008-07-07 13:44                         ` Matthieu
2008-07-07 13:55                           ` Philippe Gerum
     [not found]                             ` <5c3287e115e89c7cbb7c53402762cb2c@domain.hid>
2008-07-07 14:16                               ` Philippe Gerum [this message]
     [not found]                                 ` <a01245292d763fa02c3e6b9a79b67348@domain.hid>
2008-07-07 14:41                                   ` Philippe Gerum
2008-07-15  7:27                                     ` Matthieu
2008-07-15 19:07                                       ` Philippe Gerum
2008-07-16  6:41                                         ` Matthieu
2008-07-16  6:28                                           ` Philippe Gerum
     [not found] <488DC8B8.4080403@domain.hid>
2008-08-07  8:12 ` Matthieu
2008-07-17  7:49 Matthieu
2008-07-21 14:41 ` Matthieu
2008-07-28 10:27   ` Matthieu
2008-07-28 13:02     ` Gilles Chanteperdrix
     [not found] <485F7A69.7080004@domain.hid>
     [not found] ` <5b5edafe752e2ab744303b0262edc05c@domain.hid>
2008-06-23 15:57   ` Philippe Gerum
2008-06-23 16:33     ` Gilles Chanteperdrix
2008-06-23 16:40       ` Philippe Gerum
2008-06-23 16:46         ` Gilles Chanteperdrix
     [not found]         ` <485FD32C.3040902@domain.hid>
2008-06-23 17:18           ` Philippe Gerum
2008-06-23 17:52             ` Matthieu
2008-06-24 14:22               ` Matthieu
  -- strict thread matches above, loose matches on Subject: below --
2008-06-23  8:14 Matthieu
2008-06-23  9:58 ` Philippe Gerum
2008-06-11  9:18 Matthieu
2008-06-11 12:28 ` Gilles Chanteperdrix
2008-06-10  8:43 Matthieu
2008-06-10  9:22 ` Matthieu
2008-06-10  9:43 ` Gilles Chanteperdrix
2008-06-11  5:47   ` Matthieu
2008-06-15 12:50     ` Gilles Chanteperdrix

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=48722544.7090203@domain.hid \
    --to=rpm@xenomai.org \
    --cc=matthieu.connaulte_xenomai@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.