This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Need clarification for cyg_mbox_timed_get()
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Jay Foster <jay dot foster at systech dot com>
- Cc: eCos Disuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 18 Jun 2004 14:03:50 +0200
- Subject: Re: [ECOS] Need clarification for cyg_mbox_timed_get()
- References: <80B97DE95AEED311BA580050047FE98494FA74@mail.systech.com>
Nick has already answered, but....
On Thu, Jun 17, 2004 at 11:05:23AM -0700, Jay Foster wrote:
> The documentation for cyg_mbox_timed_get() states that it "will wait until
> either a message is available or until a number of clock ticks have
> occurred."
To fully quote the documentation:
There are two variants of cyg_mbox_get. The first, cyg_mbox_timed_get
will wait until either a message is available or until a number of
clock ticks have occurred. The number of ticks is specified as an
absolute, not relative tick count, and so in order to wait for a
relative number of ticks, the return value of the cyg_current_time()
function should be added to determine the absolute number of ticks.
> I assumed it was clock ticks occurred since the call to
> cyg_mbox_timed_get(), but it seems to behave as if it is clock ticks
> occurred since boot time (not as useful). What is the correct behavior?
Question: Why is it not as useful?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss