All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Roderik_Wildenburg@domain.hid, Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] pthread_make_periodic_np and clock_gettime
Date: Wed, 14 Feb 2007 18:44:15 +0100	[thread overview]
Message-ID: <45D34A6F.9050406@domain.hid> (raw)
In-Reply-To: <17874.6444.25366.622467@domain.hid>

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

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>  > Roderik_Wildenburg@domain.hid wrote:
>  > > Can anybody tell me, how I have to set the 2. parameter (starttp) of
>  > > pthread_make_periodic_np ?
>  > > When I use clock_gettime to fill startp I get a giant timeout value in
>  > > the /proc/xenomai/sched list and my task never gets periodic.
>  > > 
>  > > Is this just a problem of my hardware(PPC)/xenomai(2.3) combination or
>  > > does anybody else have the same problem. 
>  > > 
>  > > See attached code example for easier testing.
>  > > 
>  > 
>  > Confirmed over v2.3.x in periodic mode, aperiodic is fine. Gilles?
> 
> Ok. I will have a look at it.
> 

Hmm, something went wrong here. I think I passed a too fast tick_arg to
the kernel yesterday which smashed the timing. I'm now running the
pperiodic demo at tick_arg=1000000 successfully.

So, Roderik, either you did some similar mistake, or it's a PPC issue.

Jan


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

      reply	other threads:[~2007-02-14 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 12:07 [Xenomai-help] pthread_make_periodic_np and clock_gettime Roderik_Wildenburg
2007-02-13 19:20 ` Jan Kiszka
2007-02-13 20:01   ` Gilles Chanteperdrix
2007-02-14 17:44     ` 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=45D34A6F.9050406@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Roderik_Wildenburg@domain.hid \
    --cc=Xenomai-help@domain.hid \
    --cc=gilles.chanteperdrix@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.