From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] A "pipe" like object for eCos?
Date: Thu, 29 May 2008 18:28:00 -0000 [thread overview]
Message-ID: <g1msii$4jk$1@ger.gmane.org> (raw)
I find myself in need of a "pipe" like object in an eCos
application (one that doesn't have file I/O and Posix support
enabled). All I need is a simple circular buffer in RAM with
blocking and non-blocking read/write methods. Am I correct in
my conclusion that eCos doesn't have something like that as
part of it's core functionality?
I haven't found anything like that in the docs, but I thought
I'd double-check before I go off and write something...
--
Grant Edwards grante Yow! I'm shaving!!
at I'M SHAVING!!
visi.com
--
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:[~2008-05-29 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 18:28 Grant Edwards [this message]
2008-05-29 18:32 ` Andrew Lunn
2008-05-29 22:25 ` [ECOS] " Grant Edwards
2008-05-29 22:52 ` Grant Edwards
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='g1msii$4jk$1@ger.gmane.org' \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.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).