From: Rodrigo Rosenfeld Rosas <lbocseg@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] RTDM and Timer functions
Date: Mon, 13 Mar 2006 16:25:41 -0300 [thread overview]
Message-ID: <200603131625.41508.lbocseg@domain.hid> (raw)
In-Reply-To: <4415B8C2.6000806@domain.hid>
Em Segunda 13 Mar=E7o 2006 15:24, Jan Kiszka escreveu:
>Rodrigo Rosenfeld Rosas wrote:
>> Sorry Jan, I was looking at a different documentation. Now I read the
>> right one. It is good. But I didn't understand why didn't you keep the
>> latter note: "The nucleus timer has to be started to obtain valid
>> results." I would include it before the other note.
>
>Well, it's no longer relevant for Xenomai: you can't load a driver
>without the timer being started - loading xeno_rtdm will do this.
>
>On the other hand, you are right when considering RTAI where you still
>face this obstacle. I will re-introduce the note below, but the strategy
>will remain that it's up to the user (application) to resolve this.
>
>"The system timer has to be started to obtain valid results. If this
>happens automatically or is controlled by the application depends on the
>RTDM host environment, see related documentation of the real-time Linux
>extension."
I would add a little, but significant comment with:
"The system timer has to be started to obtain valid results. If this
happens automatically (as it does on Xenomai) or is controlled by the=20
application depends on the RTDM host environment, see related documentation=
=20
of the real-time Linux extension."
Regards,
Rodrigo.
_______________________________________________________
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora!
http://br.acesso.yahoo.com
next prev parent reply other threads:[~2006-03-13 19:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 17:43 [Xenomai-core] RTDM and Timer functions Rodrigo Rosenfeld Rosas
2006-03-09 20:33 ` Jan Kiszka
2006-03-10 13:54 ` Rodrigo Rosenfeld Rosas
2006-03-10 18:32 ` Jan Kiszka
2006-03-10 20:00 ` Rodrigo Rosenfeld Rosas
2006-03-13 11:48 ` Jan Kiszka
2006-03-13 14:54 ` Rodrigo Rosenfeld Rosas
2006-03-13 17:15 ` Rodrigo Rosenfeld Rosas
2006-03-13 17:58 ` Rodrigo Rosenfeld Rosas
2006-03-13 18:24 ` Jan Kiszka
2006-03-13 19:25 ` Rodrigo Rosenfeld Rosas [this message]
2006-03-13 19:19 ` Rodrigo Rosenfeld Rosas
2006-03-15 4:44 ` Jim Cromie
2006-03-13 18:12 ` Jan Kiszka
2006-03-14 1:28 ` Rodrigo Rosenfeld Rosas
2006-03-13 17:25 ` Gilles Chanteperdrix
2006-03-13 17:31 ` Rodrigo Rosenfeld Rosas
2006-03-13 18:33 ` Jan Kiszka
2006-03-13 19:31 ` Rodrigo Rosenfeld Rosas
2006-03-13 23:05 ` Jan Kiszka
2006-03-14 1:36 ` Rodrigo Rosenfeld Rosas
2006-03-14 6:44 ` Jan Kiszka
2006-03-14 14:27 ` Rodrigo Rosenfeld Rosas
2006-03-14 16:46 ` Jan Kiszka
2006-03-14 16:59 ` Rodrigo Rosenfeld Rosas
2006-03-14 18:45 ` Rodrigo Rosenfeld Rosas
2006-03-14 19:00 ` Jan Kiszka
2006-03-14 19:40 ` Rodrigo Rosenfeld Rosas
2006-03-14 20:29 ` Jan Kiszka
2006-03-14 22:32 ` Rodrigo Rosenfeld Rosas
2006-03-14 22:51 ` Jan Kiszka
2006-03-15 0:31 ` Rodrigo Rosenfeld Rosas
2006-03-15 13:06 ` Philippe Gerum
[not found] ` <44167BE9.2090703@domain.hid>
2006-03-14 10:16 ` Jan Kiszka
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=200603131625.41508.lbocseg@domain.hid \
--to=lbocseg@domain.hid \
--cc=jan.kiszka@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.