From: "Andrew Hannam" <andrewh@inmarket.com.au>
To: "'eCos Discussion'" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Couple of porting questions
Date: Tue, 24 Jun 2014 15:05:00 -0000 [thread overview]
Message-ID: <002601cf8fbd$3ff8bad0$bfea3070$@inmarket.com.au> (raw)
In-Reply-To:
I am currently porting the uGFX LCD graphics library to eCos and have a few
questions.
1/ Is there any method of detecting from a thread handle whether the thread
that handle refers to is still runnable ie. hasn't exited or been killed?
2/ Is there any way of detecting if cyg_scheduler_start() has already been
called or, is it safe to call it multiple times with no side effects or, can
it be assumed that cyg_scheduler_start() has already been called when main()
is invoked (if the kernel is included)?
3/ Is there any approved method of halting the system (eg due to an
unrecoverable soft error) or is calling the C library exit() or _exit()
sufficient?
4/ Can stdout output be relied upon on all platforms? Is stdout and/or
stderr assumed to be a debug/monitor output stream?
Thanks,
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
next reply other threads:[~2014-06-24 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 15:05 Andrew Hannam [this message]
2014-06-24 22:34 ` [ECOS] " John Dallaway
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='002601cf8fbd$3ff8bad0$bfea3070$@inmarket.com.au' \
--to=andrewh@inmarket.com.au \
--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).