From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Sherrill To: elix@sourceware.cygnus.com Subject: Elix and RTEMS Date: Tue, 30 Nov 1999 18:59:00 -0000 Message-id: <38448ED0.BF5974B8@OARcorp.com> X-SW-Source: 1999-q4/msg00001.html 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