From: "Venkateswara Rao L." <lvenkat@lvl7.com>
To: <czimman@bloomberg.com>, <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Pipes in eCos
Date: Fri, 27 Apr 2007 11:20:00 -0000 [thread overview]
Message-ID: <FE7FB54DCB7C6949A1D3F9FF22DA6C13509AC2@lvl7in-mail01.lvl7.com> (raw)
Chris
My requirement is to do some communication among threads .I can use MSGQ
for this. But I need to use select with the communication mechanism. As
using select is proving to be quite generic for my requirement. I've to
put additional infrastructure if i use msgqs.
L.Venkateswara Rao
-----Original Message-----
From: czimman@bloomberg.com [mailto:czimman@bloomberg.com]
Sent: Friday, April 27, 2007 2:28 PM
To: Venkateswara Rao L.; ecos-discuss@ecos.sourceware.org
Subject: RE: [ECOS] Pipes in eCos
eCos doesn't have processes, so pipes wouldn't be particularly useful.
You could certainly create a pipe emulation mechanism, but what is it
that you're trying to do?
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of
Venkateswara Rao L.
Sent: 27 April 2007 09:55
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Pipes in eCos
Hi all,
It seams eCos does not support pipes, is there anything
equivalent to that?
Warm Regards,
L.Venkateswara Rao.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
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:[~2007-04-27 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 11:20 Venkateswara Rao L. [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-27 8:54 Venkateswara Rao L.
2007-04-27 8:57 ` Chris Zimman
2007-04-27 9:46 ` Andrew Lunn
2007-04-27 11:24 ` Richard Pennington
2007-04-27 13:59 ` Andrew Lunn
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=FE7FB54DCB7C6949A1D3F9FF22DA6C13509AC2@lvl7in-mail01.lvl7.com \
--to=lvenkat@lvl7.com \
--cc=czimman@bloomberg.com \
--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).