[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
clock_nanosleep
- Date: Mon, 25 Feb 2008 10:41:09 -0600
- From: joel.sherrill at OARcorp.com (Joel Sherrill)
- Subject: clock_nanosleep
Moro, Pierre wrote:
> Hello everyone,
>
> I'm trying to build some application for a LEON3 proc.
> this application uses clock_nanosleep which seems to be part of a
> real-time extension of posix and this function is not found while
> compiling for leon3 target ( I use the rtems-4.7.99.2 tar given by
> gaisler on their website for compiling my project).
>
> Does anyone have any idea if
> a) I'm doing something bad and I should find this function
> b) or if this is not (yet?) implemented.
>
It is in the not implemented category.
> In the latter case, how long do you think it would take to implement
> it ? knowing that I'm just starting with rtems.
>
Are you just trying to delay? Are you really trying to send a POSIX
signal? Right now, the only POSIX clock that works is
the one that would be used with nanosleep() or usleep().
It shouldn't be hard to implement based upon what I read
in the opengroup.org specification if all you want is CLOCK_REALTIME.
If you want me to put together an estimate for you of what
it would take for me to implement it for you, I would be
happy to do that after a bit of discussion on what CLOCK_XXX
values you wanted to support. Remember there are at least
these CLOCKS:
+ CLOCK_REALTIME
+ CLOCK_MONOTONIC
+ CLOCK_PROCESS_CPUTIME
+ CLOCK_THREAD_CPUTIME
So I would want to make sure your real requirement was met.
--joel
> thx
>
> Pierre
>
>
>
> Pierre Moro, ASTRIUM ST
> Tel: +33 (0)1 39 06 72 64 Fax: +33 (0)1 39 06 27 97
> Site:* LES MUREAUX* BD: *19* Floor: *1* Room: *141*
>
> ------------------------------------------------------------------------
> Ce courriel (incluant ses ?ventuelles pi?ces jointes) peut contenir
> des informations confidentielles et/ou prot?g?es ou dont la diffusion
> est restreinte. Si vous avez re?u ce courriel par erreur, vous ne
> devez ni le copier, ni l?utiliser, ni en divulguer le contenu ?
> quiconque. Merci d?en avertir imm?diatement l?exp?diteur et d'effacer
> ce courriel de votre syst?me. Astrium d?cline toute responsabilit? en
> cas de corruption par virus, d?alt?ration ou de falsification de ce
> courriel lors de sa transmission par voie ?lectronique.
> This email (including any attachments) may contain confidential and/or
> privileged information or information otherwise protected from
> disclosure. If you are not the intended recipient, please notify the
> sender immediately, do not copy this message or any attachments and do
> not use it for any purpose or disclose its content to any person, but
> delete this message and any attachments from your system. Astrium
> disclaims any and all liability if this email transmission was virus
> corrupted, altered or falsified.
> ---------------------------------------------------------
> Astrium SAS (393 341 516 RCS Paris) ? Capital: 16.587.728 EUR ? Si?ge
> social: 6 rue Laurent Pichat, 75016 Paris, France
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985