From: lesc <lesc@zhaw.ch>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Once again, I need a binary semaphore
Date: Tue, 17 Mar 2015 09:21:00 -0000 [thread overview]
Message-ID: <5507F21B.1000900@zhaw.ch> (raw)
In-Reply-To: <me737v$ojs$1@ger.gmane.org>
On 16.03.2015 18:17, Grant Edwards wrote:
> Once again, I find I need a binary semaphore for a C application I'm
> porting from another OS.
And just using a mutex is not a option? (Sorry if you allready ruled
that out, but you didn't metion why youd need that specific sync-mechanism).
Serafin
--
Serafin Leschke, BSc in Computer Sience UAS Zurich
Research Assistant
ZHAW, Zurich University of Applied Sciences
InES, Institute of Embedded Systems
Postfach
Technikumstr. 22
CH-8401 Winterthur
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2015-03-17 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 17:18 Grant Edwards
2015-03-17 9:21 ` lesc [this message]
2015-03-17 14:33 ` [ECOS] " Grant Edwards
2015-03-17 14:47 ` Grant Edwards
2015-03-17 14:57 ` Frank Pagliughi
2015-03-17 15:19 ` Grant Edwards
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=5507F21B.1000900@zhaw.ch \
--to=lesc@zhaw.ch \
--cc=ecos-discuss@ecos.sourceware.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 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).