From: Andrew Lunn <andrew@lunn.ch>
To: Richard Pennington <rich@pennware.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Pipes in eCos
Date: Fri, 27 Apr 2007 13:59:00 -0000 [thread overview]
Message-ID: <20070427135912.GA28128@lunn.ch> (raw)
In-Reply-To: <4631DD2E.4030300@pennware.com>
On Fri, Apr 27, 2007 at 06:23:26AM -0500, Richard Pennington wrote:
> Andrew Lunn wrote:
> >On Fri, Apr 27, 2007 at 02:24:39PM +0530, Venkateswara Rao L. wrote:
> >>Hi all,
> >>
> >> It seams eCos does not support pipes, is there anything
> >>equivalent to that?
> >
> >Take a look at the thread:
> >
> >http://www.cygwin.com/ml/ecos-patches/2004-12/msg00034.html
> >
> >It was decided not to include it because it does not really follow the
> >eCos way of doing things, but that should not stop you from using it
> >is you want.
> >
> > Andrew
> >
>
> Hi Andrew,
>
> Out of curiosity, how does that pipe/pty implementation fall short for
> eCos? I've been thinking of using it to get a select()-able file
> descriptor for inter-thread communication.
>
> Are there improvements that could be made to make it fit into eCos
> better? I'd be willing to give it a try. Otherwise I'll just use my
> version quietly.
There was discussion at the time. What does the archive say? It is
something like two years ago, so i don't remember myself.
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 prev parent reply other threads:[~2007-04-27 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2007-04-27 11:20 Venkateswara Rao L.
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=20070427135912.GA28128@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rich@pennware.com \
/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).