This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
What to use instead of pipe?
- From: "Konstantin Azarov" <azarov at comtv dot ru>
- To: <ecos-devel at sources dot redhat dot com>
- Date: Wed, 14 Apr 2004 01:00:56 +0400
- Subject: What to use instead of pipe?
- Fl-build: Fidolook Express 2001 UIExt. BuildID: 3BC00FAD (7/10/2001 12:17:49).
Hello!
I'm currently writing a eCOS application and came upon the following
problem. In my application I have the menu, which must be accessible through
UART and Telnet. I'm going to handle the menu via standart files. The first
problem is that I've to write special filesystem to handle telnet sessions.
But this seems quite straitforward. The second problem is more interesting.
UART traffic must be filtered, that is, program must perform certain actions
as the reaction to certain input sequences (for example, if it sees "%%%" in
the UART input, it has, say, to turn on LED. At the same time, Telnet
traffic must not be filtered in this way. The solution, I wanted to
implement, was like this. I was going to create a "filter" thread, wich
would actually read data from UART and would open a pipe. Filtered traffic
would go through the pipe to the menu. The issue is that pipes are not
implemented in eCOS. Could you tell me, what can I use instead of pipe()? Or
may be it will be easier to implement something like pipe()?
By the way, it seems that implementing telnet with pipes will be much
better.
Thanks in advice,
Konstantin Azarov