summaryrefslogtreecommitdiffstats
path: root/doc/posix_users
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1999-11-16 19:41:31 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1999-11-16 19:41:31 +0000
commit8f9efcb994264470f323034b5f024e52f5898a24 (patch)
treee212f89713f26ef1239ee021c781e2f47997ce47 /doc/posix_users
parentAdded reference to rtems_get_class, rtems_get_node, and rtems_get_index (diff)
downloadrtems-8f9efcb994264470f323034b5f024e52f5898a24.tar.bz2
Added status chapter.
Diffstat (limited to 'doc/posix_users')
-rw-r--r--doc/posix_users/Makefile9
-rw-r--r--doc/posix_users/posix_users.texi2
-rw-r--r--doc/posix_users/status.t64
3 files changed, 73 insertions, 2 deletions
diff --git a/doc/posix_users/Makefile b/doc/posix_users/Makefile
index c33a6d07fe..f4f1f1c0e9 100644
--- a/doc/posix_users/Makefile
+++ b/doc/posix_users/Makefile
@@ -21,8 +21,8 @@ GENERATED_FILES= \
cancel.texi clock.texi cond.texi \
cspecific.texi device.texi files.texi \
io.texi key.texi memorymgmt.texi message.texi mutex.texi procenv.texi \
- process.texi sched.texi semaphores.texi signal.texi systemdb.texi \
- thread.texi
+ process.texi sched.texi semaphores.texi signal.texi status.texi \
+ systemdb.texi thread.texi
FILES= posix_users.texi preface.texi \
$(COMMON_FILES) $(GENERATED_FILES)
@@ -154,3 +154,8 @@ systemdb.texi: systemdb.t Makefile
-u "Top" \
-n "" ${*}.t
+status.texi: status.t Makefile
+ $(BMENU) -p "" \
+ -u "Top" \
+ -n "" ${*}.t
+
diff --git a/doc/posix_users/posix_users.texi b/doc/posix_users/posix_users.texi
index 28d34ac051..88918901a6 100644
--- a/doc/posix_users/posix_users.texi
+++ b/doc/posix_users/posix_users.texi
@@ -103,6 +103,7 @@ END-INFO-DIR-ENTRY
@include thread.texi
@include key.texi
@include cancel.texi
+@include status.texi
@ifinfo
@node Top, Preface, (dir), (dir)
@top posix_users
@@ -129,6 +130,7 @@ This is the online version of the RTEMS POSIX API User's Guide
* Thread Manager::
* Key Manager::
* Thread Cancellation Manager::
+* Status of Implementation::
* Command and Variable Index::
* Concept Index::
@end menu
diff --git a/doc/posix_users/status.t b/doc/posix_users/status.t
new file mode 100644
index 0000000000..a32c336e47
--- /dev/null
+++ b/doc/posix_users/status.t
@@ -0,0 +1,64 @@
+@c
+@c COPYRIGHT (c) 1988-1998.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+@c $Id$
+@c
+
+@chapter Status of Implementation
+
+This chapter provides an overview of the status of the implementation
+of the POSIX API for RTEMS. The @i{POSIX 1003.1b Compliance Guide}
+provides more detailed information regarding the implementation of
+each of the numerous functions, constants, and macros specified by
+the POSIX 1003.1b standard.
+
+RTEMS supports many of the process and user/group oriented services
+in a "single user/single process" manner. This means that although
+these services may be of limited usefulness or functionality, they
+are provided and do work in a coherent manner. This is significant
+when porting existing code from UNIX to RTEMS.
+
+@itemize @bullet
+@item Implementation
+@itemize @bullet
+@item The current implementation of @code{dup()} is insufficient.
+@item FIFOs @code{mkfifo()} are not currently implemented.
+@item Asynchronous IO is not implemented.
+@item Blocking Send for Message Queues is not implemented
+@item The @code{flockfile()} family is not implemented
+@item getc/putc unlocked family is not implemented
+@item Shared Memory is not implemented
+@item Mapped Memory is not implemented
+@item NOTES:
+@itemize @bullet
+@item For Shared Memory and Mapped Memory services, it is unclear what
+level of support is appropriate and possible for RTEMS.
+@end itemize
+@end itemize
+
+
+@item Functional Testing
+@itemize @bullet
+@item Named Semaphores are untested.
+@item There is currently no Message Queue test.
+@item Tests for unimplemented services
+@end itemize
+
+@item Performance Testing
+@itemize @bullet
+@item There are no POSIX Performance Tests.
+@end itemize
+
+@item Documentation
+@itemize @bullet
+@item Most of the service description pages are completed in this
+manual. These need to be completed and information added to the
+background and operations sections.
+@item Example programs (not just tests) would be very nice.
+@end itemize
+
+@end itemize
+
+