| WP1 - RTOS State of the Art Analysis: Deliverable D1.1 - RTOS Analysis | ||
|---|---|---|
| Prev | Chapter 10. RTEMS 4.5+ | Next |
Graphic support depends on BSP package
There are configuration and known applications using graphics frame-buffer and there exists MicroWindows and Nano-X port for RTEMS executive.
Development environment: GCC and other GNU tools. Remote debugging via serial line or Ethernet.
Fail signal and recovery: setjmp/longjmp
Supported programming languages: C, C++, ADA
RTEID/ORKID based Classic API.
uITRON 3.0 API in development.
ADA language API for RT systems.
POSIX 1003.1b API including threads.
The implementation status can be sketched by one section from reported compliance summary which shows next numbers for 362 POSIX 1003.1b functions defined by standard.
Implemented : 301
Unimplemented : 21
Unimplementable : 16
Partial : 2
Dummy : 19
Untested : 1
Following is a list of the most important lacking functionalities of current version of RTEMS executive.
The current implementation of dup() is insufficient.
FIFOs mkfifo() are not currently implemented.
Asynchronous IO is not implemented.
The flockfile() family is not implemented
getc/putc unlocked family is not implemented
Shared Memory is not implemented