From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: elix@sourceware.cygnus.com
Subject: Elix and RTEMS
Date: Tue, 30 Nov 1999 18:59:00 -0000 [thread overview]
Message-ID: <38448ED0.BF5974B8@OARcorp.com> (raw)
As I understood some of the early information on Elix, it was
intended to be a standard/specification for embedded POSIX as
well as an implementation. Given this understanding, I would
like to offer RTEMS as an existing implementation of the Elix
specification.
Today, as best I can tell from the information I
have seen, RTEMS includes nearly every POSIX feature
required by the specification. At this point, RTEMS
includes the following mentioned in the Elix specification:
+ approximately 85% of the functionality of POSIX 1003.1b
including POSIX threads, signals, etc.
+ a port of the FreeBSD TCP/IP stack
Other features include:
+ filesystem support
+ httpd web server (GoAhead)
+ ftpd server
+ numerous network client services including DNS and TFTP
+ Classic API (based on same specification as pSOS+)
+ initial ITRON 3.0 support
+ remote debugging via Ethernet
+ multiprocessor support
RTEMS provides this functionality today for deeply embedded systems.
Elix is a new presentation of ideas espoused by the RTEMS Team for
years.
By providing compatability with standards, third party software can be
ported
easily to the RTEMS environment. This has enabled a variety of packages
including CORBAS, TCL, zlib, libavl, and ncurses to be easily ported to
RTEMS. More often than not, it is just a matter of passing the right
options to configure. :)
Basically, I just want to make sure that RTEMS gets a fair technical
shake
as an alternative -- and existing -- implementation of Elix for embedded
systems.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
reply other threads:[~1999-11-30 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=38448ED0.BF5974B8@OARcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=elix@sourceware.cygnus.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).