From: Stanislav Meduna <stano@meduna.org>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: scheduler started?
Date: Fri, 12 Aug 2011 13:35:00 -0000 [thread overview]
Message-ID: <4E452C1C.5090407@meduna.org> (raw)
On 12.08.2011 09:03, Slide wrote:
> Back in 2009, this [1] message told one way to know if the scheduler
> was already started. Is this still the recommended method for doing
> so?
>
> [1] - http://sourceware.org/ml/ecos-discuss/2009-06/msg00105.html
I'd like to ask the same question. I have an I2C RTC chip that
has to be accessed in the wallclock constructor. Contrary
to the SPI the I2C does not allow to force the polled mode
in the transfer function calls (by design choice - see
http://www.cygwin.com/ml/ecos-patches/2006-10/msg00015.html -
that I find quite unfortunate).
Before resorting to ugly hacks or patching the scheduler itself
to set some flag, is
cyg_thread_self() == cyg_thread_idle_thread()
still safe and recommended for this purpose?
Thanks
--
Stano
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2011-08-12 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E452C1C.5090407@meduna.org \
--to=stano@meduna.org \
--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).