From: cetoni GmbH - Uwe Kindler <uwe.kindler@cetoni.de>
To: Alexey Shusharin <mrfinch@mail.ru>
Cc: ecos-discuss@sourceware.org
Subject: [ECOS] Re: Waiting I/O operation
Date: Thu, 19 Jul 2007 10:39:00 -0000 [thread overview]
Message-ID: <469F3EE4.3090401@cetoni.de> (raw)
In-Reply-To: <469F3371.2000204@mail.ru>
Hello Alexey,
if it is allowed to set flags from DSR (is there a documentation about
this somewhere?!?) I would agree with the callback solution.
You could implement support for registering callback functions at
runtime by calling cyg_io_set_config. The callback function should be
called by CAN I/O layer after the received event is stored into the
event queue. Support for callback functions should be configurable via CDL.
In the callback function you could call cyg_flag_setbits() to signal the
thread that a new event was received.
Regards, Uwe
Dipl. Inf. (FH)
Uwe Kindler
Software Engineering
--
cetoni GmbH
Am Wiesenring 6
D-07554 Korbussen
Tel.: +49 (0) 36602 338 28
Fax: +49 (0) 36602 338 11
uwe.kindler@cetoni.de
www.cetoni.de
--
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:[~2007-07-19 10:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 8:47 cetoni GmbH - Uwe Kindler
2007-07-19 9:53 ` Alexey Shusharin
2007-07-19 10:39 ` cetoni GmbH - Uwe Kindler [this message]
2007-07-19 10:56 ` Alexey Shusharin
2007-07-19 10:41 ` Alexey Shusharin
2007-07-19 10:47 ` Sergei Gavrikov
2007-07-20 19:35 ` Andrew Lunn
2007-07-21 11:22 ` Sergei Gavrikov
2007-07-21 13:21 ` Uwe Kindler
2007-07-21 15:11 ` Sergei Gavrikov
2007-07-21 15:25 ` Sergei Gavrikov
2007-07-23 4:10 ` Alexey Shusharin
2007-07-23 5:53 ` Uwe Kindler
2007-07-23 9:12 ` Sergei Gavrikov
2007-07-23 10:15 ` Alexey Shusharin
2007-07-23 18:49 ` Sergei Gavrikov
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=469F3EE4.3090401@cetoni.de \
--to=uwe.kindler@cetoni.de \
--cc=ecos-discuss@sourceware.org \
--cc=mrfinch@mail.ru \
/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).