public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Carsten Andersen <Carsten.Andersen@csr.com>
To: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] pthread_cond_timedwait() and absolute time?
Date: Wed, 19 Jun 2002 09:05:00 -0000	[thread overview]
Message-ID: <AE087AD7160474448283E09975B1161A4BFB6C@exchange01.csr.com> (raw)

The pthread_cond_timedwait() function's 3rd parameter is a timespec
structure containing absolute time. The clock_gettime() function does not
support TIMER_ABSTIME. So how do I get hold of the absolute time that the
pthread_cond_timedwait() function wants? I've tried to use the
CLOCK_REALTIME id instead (and adding my delta time), but that doesn't work
properly when used in the pthread_cond_timedwait() function?


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2002-06-19 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19  9:05 Carsten Andersen [this message]
2002-06-20 15:46 ` Nick Garnett
     [not found] <AE087AD7160474448283E09975B1161A4BFB6F@exchange01.csr.com>
2002-06-21 12:10 ` Nick Garnett

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=AE087AD7160474448283E09975B1161A4BFB6C@exchange01.csr.com \
    --to=carsten.andersen@csr.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).