summaryrefslogtreecommitdiffstats
path: root/doc/relnotes
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1997-05-27 12:40:11 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1997-05-27 12:40:11 +0000
commitae68ff085724dd35d60151bd153e80b8b0776873 (patch)
tree2f1535a0497f5b872a4744ae13c9264b77e89c11 /doc/relnotes
parentb65131dc23672b24c32d76081c5917f2f38d93fe (diff)
downloadrtems-ae68ff085724dd35d60151bd153e80b8b0776873.tar.bz2
Initial revision
Diffstat (limited to 'doc/relnotes')
-rw-r--r--doc/relnotes/Makefile53
-rw-r--r--doc/relnotes/install.texi174
-rw-r--r--doc/relnotes/intro.texi223
-rw-r--r--doc/relnotes/probrep.texi60
-rw-r--r--doc/relnotes/relnotes.texi116
-rw-r--r--doc/relnotes/status.texi258
6 files changed, 884 insertions, 0 deletions
diff --git a/doc/relnotes/Makefile b/doc/relnotes/Makefile
new file mode 100644
index 0000000000..e50a845f11
--- /dev/null
+++ b/doc/relnotes/Makefile
@@ -0,0 +1,53 @@
+#
+# COPYRIGHT (c) 1996.
+# On-Line Applications Research Corporation (OAR).
+# All rights reserved.
+#
+
+include ../Make.config
+
+PROJECT=relnotes
+
+all:
+
+COMMON_FILES=../common/cpright.texi
+
+FILES=install.texi intro.texi probrep.texi relnotes.texi status.texi
+
+all:
+
+info: relnotes
+ cp $(PROJECT) $(wildcard $(PROJECT)-*) $(INFO_INSTALL)
+
+relnotes: $(FILES)
+ $(MAKEINFO) $(PROJECT).texi
+
+vinfo: info
+ $(INFO) -f relnotes
+
+dvi: $(PROJECT).dvi
+ps: $(PROJECT).ps
+
+$(PROJECT).ps: $(PROJECT).dvi
+ dvips -o $(PROJECT).ps $(PROJECT).dvi
+ cp $(PROJECT).ps $(PS_INSTALL)
+
+view: ps
+ $(GHOSTVIEW) $(PROJECT).ps
+
+dv: dvi
+ $(XDVI) $(PROJECT).dvi
+
+$(PROJECT).dvi: $(FILES)
+ $(TEXI2DVI) $(PROJECT).texi
+
+html:
+ -mkdir $(WWW_INSTALL)/relnotes
+ $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \
+ $(PROJECT).texi
+
+clean:
+ rm -f *.o $(PROG) *.txt core *.html
+ rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE)
+ rm -f relnotes relnotes-* _*
+
diff --git a/doc/relnotes/install.texi b/doc/relnotes/install.texi
new file mode 100644
index 0000000000..3f79e39da5
--- /dev/null
+++ b/doc/relnotes/install.texi
@@ -0,0 +1,174 @@
+@c
+@c COPYRIGHT (c) 1988-1996.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+
+@ifinfo
+@node Installation Procedure, Installation Procedure Introduction, Introduction Documentation, Top
+@end ifinfo
+@chapter Installation Procedure
+@ifinfo
+@menu
+* Installation Procedure Introduction::
+* Installation Procedure RTEMS FTP Site Organization::
+* Installation Procedure Unarchiving the RTEMS and GNU Components::
+* Installation Procedure Installing a Cross-Development GNU Toolset::
+* Installation Procedure Installing RTEMS::
+@end menu
+@end ifinfo
+
+@ifinfo
+@node Installation Procedure Introduction, Installation Procedure RTEMS FTP Site Organization, Installation Procedure, Installation Procedure
+@end ifinfo
+@section Introduction
+
+This chapter describes the process of installing and
+configuring RTEMS and a cross-development environment based on
+freely available tools and libraries.
+
+@ifinfo
+@node Installation Procedure RTEMS FTP Site Organization, Installation Procedure Unarchiving the RTEMS and GNU Components, Installation Procedure Introduction, Installation Procedure
+@end ifinfo
+@section RTEMS FTP Site Organization
+
+RTEMS is distributed only via anonymous ftp.
+
+This section will discuss how to navigate the RTEMS
+ftp site and unarchive the files in the RTEMS and GNU package
+distributions. All example commands will be given in a shell
+independent fashion unless otherwise noted.
+
+Throughout the rest of this manual
+<RTEMS_distribution> will be used as the parent of components
+within the RTEMS distribution. For persons using the ftp
+distribution found on the primary ftp site for RTEMS,
+<RTEMS_distribution> is
+ftp://ftp.OARcorp.com/oarcorp/rtems/@value{RTEMS-RELEASE}.
+
+The archive files for RTEMS Release @value{RTEMS-RELEASE} are found
+under the directory <RTEMS_distribution>. This directory
+contains the files which comprise this relase as well as any
+patches which may be required for other tools.
+
+The complete source code and documentation set for
+the C language implementation of RTEMS is provided.
+
+Documentation other than this on-line version is available to
+OAR support customers. Please contact OAR for more information.
+
+@ifinfo
+@node Installation Procedure Unarchiving the RTEMS and GNU Components, Installation Procedure Installing a Cross-Development GNU Toolset, Installation Procedure RTEMS FTP Site Organization, Installation Procedure
+@end ifinfo
+@section Unarchiving the RTEMS and GNU Components
+
+Many of the components of the RTEMS release are
+"tarred, zipped" files and have the .tar.gz or .tgz extension.
+The GNU zip package is required to unarchives these files on the
+RTEMS ftp site. If this package is not installed, the source
+can be found in the files
+ftp://prep.ai.mit.edu/pub/gnu/gzip-1.2.4.shar or
+ftp://prep.ai.mit.edu/pub/gnu/gzip-1.2.4.tar. It may be
+restored using a command similar to the following:
+
+@example
+@group
+tar xvf gzip-1.2.4.tar
+
+OR
+
+sh gzip-1.2.4.shar
+@end group
+@end example
+
+This will create a subdirectory gzip-1.2.4 in the
+current directory. Please examine the files README and INSTALL
+and follow the instructions provided there.
+
+[Note: The GNU tools follow a standard packaging procedure
+They will unarchive into a directory based on the package name and version
+number. For detailed instructions on compilation and
+installation of the GNU tools, please refer to the instructions for
+each GNU tool.]
+
+Files which have been "tarred, zipped" (i.e. .tar.gz
+or .tgz extension) may be unarchived with a command similar to
+one of the following:
+
+@example
+@group
+gzcat <file>.tgz | tar xvof -
+
+OR
+
+gunzip -c <file>.tgz | tar xvof -
+
+OR
+
+gtar xzvf <file>.tgz
+@end group
+@end example
+
+NOTE: gunzip -c is equivalent to gzcat, while gtar is GNU tar.
+
+Given that the necessary utility programs are
+installed, any of the above commands will extract the contents
+of <file>.tar.gz into the current directory. All of the RTEMS
+components will be extracted into the subdirectory rtems-@value{RTEMS-RELEASE}.
+To view the contents of a component without restoring any files,
+use a command similar to the following:
+
+@example
+@group
+gzcat <file>.tgz | tar tvf -
+@end group
+@end example
+
+@ifinfo
+@node Installation Procedure Installing a Cross-Development GNU Toolset, Installation Procedure Installing RTEMS, Installation Procedure Unarchiving the RTEMS and GNU Components, Installation Procedure
+@end ifinfo
+@section Installing a Cross-Development GNU Toolset
+
+This sections describes how to build and install the
+FSF GNU tools for use as a cross-compilation system. These
+tools are used by the RTEMS developers. Every effort has been
+made to make these instructions accurate and complete. However,
+it is recommended that the individual doing the installation
+read the appropriate installation notes for each of the tools in
+the cross toolset. This will help insure that there are no
+special requirements for a particular host.
+
+If the host and target processors are the same, then
+it may be possible to use the host development tools. An
+example of this scenario is using a SPARC based workstation
+to develop an RTEMS application for the SPARC processor. Although
+the native toolset is useable in this scenario, it is ultimately
+more desirable to build a toolset specifically for the embedded environment.
+
+Instructions for building a cross environment using the GNU
+tools is provided in the crossgcc FAQ available from ftp.cygnus.com
+in /pub/embedded/crossgcc. It is recommended that the user following
+these instructions.
+
+After the cross development toolset has been built
+and installed, it will be necessary to modify the environment of
+each RTEMS application developer to reflect at least the path of
+the newly installed cross development toolset.
+
+The documentation for the FSF GNU and Cygnus tools is
+formatted using TeX. The RTEMS developers use TeX 3.14t3 to
+format the manuals for their own use. This document does not
+contain instructions on the acquisition or installation of TeX
+and supporting tools.
+
+NOTE: For "UNIX" processors, the native compiler binary utilities
+should be used.
+
+@ifinfo
+@node Installation Procedure Installing RTEMS, Development Environment Status, Installation Procedure Installing a Cross-Development GNU Toolset, Installation Procedure
+@end ifinfo
+@section Installing RTEMS
+
+For instructions on building and installing RTEMS, please refer to
+the file README.configure in the source distribution.
+
diff --git a/doc/relnotes/intro.texi b/doc/relnotes/intro.texi
new file mode 100644
index 0000000000..f185a40f17
--- /dev/null
+++ b/doc/relnotes/intro.texi
@@ -0,0 +1,223 @@
+@c
+@c COPYRIGHT (c) 1988-1996.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+
+@ifinfo
+@node Introduction, Introduction Supporting Tools, Top, Top
+@end ifinfo
+@chapter Introduction
+@ifinfo
+@menu
+* Introduction Supporting Tools::
+* Introduction Documentation::
+@end menu
+@end ifinfo
+
+This document describes the contents, installation
+procedure, and current status of Release @value{RTEMS-RELEASE} of the RTEMS
+executive. An installation procedure is provided which
+describes the steps necessary to load and configure the RTEMS
+environment, including the GNU Development Environment and the
+Cygnus NEWLIB ANSI C Library, on a host computer. The status of
+the RTEMS environment is given, which includes supported
+processors and target boards, versions of the GNU utilities
+which were used by the RTEMS developers for this release,
+support libraries status, features which are not implemented,
+and any known existing problems.
+
+This RTEMS release package contains the following general components:
+
+@itemize @bullet
+@item RTEMS C Executive
+
+@item RTEMS C Documentation Set
+
+@item RTEMS NEWLIB ANSI C Library
+
+@item Patches to GNU Development Tools
+
+@end itemize
+
+There is a mailing list dedicated to RTEMS. This is
+a Majordomo style mailing list and may be subscribed to
+by sending a message to rtems-list-request@@OARcorp.com with
+the following line as the body:
+
+@example
+subscribe rtems_user@@your_email_goes_here.com
+@end example
+
+Please replace rtems_user@@your_email_goes_here.com with your
+email address.
+
+@ifinfo
+@node Introduction Supporting Tools, GNU Development Tools, Introduction, Introduction
+@end ifinfo
+@section Supporting Tools
+@ifinfo
+@menu
+* GNU Development Tools::
+* ANSI C Libraries::
+* GNU C Library::
+* Cygnus NEWLIB C Library::
+@end menu
+@end ifinfo
+
+This section discusses the freely available tools and
+libraries which are part of the RTEMS Development Environment.
+None of the tools discussed in this section were developed by
+the RTEMS project, although many do include submissions from the
+project. All of the tools and libraries required to build RTEMS
+are freely available. The home ftp site for most of the non-RTEMS
+specific tools is either prep.ai.mit.edu (18.71.0.38) or
+ftp.cygnus.com (140.174.1.3).
+
+Specifically of interest to embedded systems developers
+using the GNU tools is the crossgcc mailing list. This is
+a Majordomo style mailing list and may be subscribed to
+by sending a message to crossgcc-request@@cygnus.com with
+the following line as the body:
+
+@example
+subscribe rtems_user@@your_email_goes_here.com
+@end example
+
+Please replace rtems_user@@your_email_goes_here.com with your
+email address. The FAQ for crossgcc is in the /pub/embedded/crossgcc
+directory on ftp.cygnus.com (205.180.83.42).
+
+@ifinfo
+@node GNU Development Tools, ANSI C Libraries, Introduction Supporting Tools, Introduction Supporting Tools
+@end ifinfo
+@subsection GNU Development Tools
+
+Numerous GNU tools are used in the RTEMS Development
+Environment including C and Ada compilers, the GNU make program,
+GNU m4, the GNU assembler and binary utilities (linker,
+librarian, etc.), GNU tar, GNU zip, and the GNU debugger. These
+tools are distributed in source form and are all licensed under
+the GNU Public License which allows for unrestricted
+distribution under the condition that source code always be
+available. The Free Software Foundation is officially the
+originator of most of the GNU tools although many individuals
+have contributed to the GNU projects. In keeping with the
+spirit of the GPL, most of the time the GNU tools are
+distributed as source code without executables. It is the
+responsibility of the local site to install each tool. Numerous
+organizations and individuals supply executables for the GNU
+tools. All are required by the terms of the GPL to also make
+the source code available to the end user.
+
+The primary ftp site for the FSF GNU tools is
+prep.ai.mit.edu (18.71.0.38) in the /pub/gnu directory. These
+tools are mirrored on numerous ftp sites.
+
+Intel maintains a toolset for their i960 processor
+family based on the GNU tools referred to as GNU/960. The
+source code for this toolset is available from ftp.intel.com
+(143.185.65.2). [NOTE: The GNU/960 toolset generally includes
+an older version of GCC than that available from the FSF. When
+the FSF version of GNU C is significantly newer than that in the
+GNU/960 release, the RTEMS developers replace the GCC in the
+GNU/960 toolset with the FSF release.]
+
+Cygnus maintains an ftp site -- ftp.cygnus.com
+(205.180.83.42) -- which contains a source code which appeals to
+embedded developers. Of especial interest on this site are the
+directories /pub/newlib and /pub/embedded.
+
+@ifinfo
+@node ANSI C Libraries, GNU C Library, GNU Development Tools, Introduction Supporting Tools
+@end ifinfo
+@subsection ANSI C Libraries
+
+This section discusses the following freely
+distributable ANSI C Libraries:
+
+@itemize @bullet
+@item GNU C Library, and
+
+@item Cygnus NEWLIB
+@end itemize
+
+No C Library is included in the standard RTEMS
+distribution. It is the responsibility of the user to obtain
+and install a C Library separately.
+
+@ifinfo
+@node GNU C Library, Cygnus NEWLIB C Library, ANSI C Libraries, Introduction Supporting Tools
+@end ifinfo
+@subsection GNU C Library
+
+The GNU C Library is a robust and well-documented C
+Library which is distributed under the terms of the Library GNU
+Public License (LGPL). This library was not designed for use in
+real-time, embedded systems and the resource requirements of
+some of the routines in this library are an obvious indication
+of this. Additionally, this library does not have support for
+reentrancy in the sense that each task in a multitasking system
+could safely invoke every routine in the library. Finally, the
+distribution terms of the LGPL are considered undesirable by
+many embedded systems developers. However, the GNU C Library is
+very complete and is compliant with as many standards as
+possible. Because of this, it may be the only choice for many
+developers.
+
+There is currently no RTEMS support for the GNU C Library.
+
+The primary ftp site for this library is
+prep.ai.mit.edu (18.71.0.38).
+
+@ifinfo
+@node Cygnus NEWLIB C Library, Introduction Documentation, GNU C Library, Introduction Supporting Tools
+@end ifinfo
+@subsection Cygnus NEWLIB C Library
+
+The Cygnus NEWLIB C Library was specifically designed
+for real-time embedded systems. It is a small, reasonably
+documented Library with support for reentrancy. This library is
+a collection of freely distributable and public domain source
+code and is freely distributable with as few restrictions as
+possible placed on the end user.
+
+The RTEMS specific support code for NEWLIB has been
+submitted to the NEWLIB maintainers and should be included in a
+future release. Until that time, it is recommended that the
+beta version of NEWLIB with RTEMS support added be used by the
+application developer. The beta version of NEWLIB with RTEMS
+specific support is ONLY available on the OAR ftp site. This
+beta version is strictly tied to a particular RTEMS release.
+
+The primary ftp site for this library is ftp.cygnus.com (205.180.83.42).
+
+@ifinfo
+@node Introduction Documentation, Installation Procedure, Cygnus NEWLIB C Library, Introduction
+@end ifinfo
+@section Documentation
+
+The RTEMS Documentation Set is provided online at http://www.OARcorp.com/
+as reference information for all levels of RTEMS users. The set includes
+the following documents:
+
+@itemize @bullet
+@item C Applications User's Guide
+
+@item Intel i386 C Applications Supplement
+
+@item Intel i960CA C Applications Supplement
+
+@item Motorola MC68xxx C Applications Supplement
+
+@item Hewlett Packard PA-RISC 1.1 C Applications Supplement
+
+@item SPARC C Applications Supplement
+
+@item Development Environment Guide
+
+@item Release Notes
+@end itemize
+
+The RTEMS documentation set is available in alternate formats to
+support customers.
diff --git a/doc/relnotes/probrep.texi b/doc/relnotes/probrep.texi
new file mode 100644
index 0000000000..54f777a030
--- /dev/null
+++ b/doc/relnotes/probrep.texi
@@ -0,0 +1,60 @@
+@c
+@c COPYRIGHT (c) 1988-1996.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+
+
+
+@ifinfo
+@node RTEMS PROBLEM REPORT, Command and Variable Index, RTEMS Problem Reporting, Top
+@end ifinfo
+@chapter RTEMS PROBLEM REPORT
+
+@example
+
+Customer (Company) Name:
+
+Customer Address:
+
+Contact Name:
+
+Telephone Voice: Fax:
+
+
+
+Product: Version:
+
+Target Processor: Target System:
+
+Host Computer System:
+
+Host Operating System: Version:
+
+
+
+Report Type: Customer Impact:
+
+
+
+[ ] Problem/Error [ ] System is inoperable, cannot proceed
+
+[ ] Enhancement [ ] Must be corrected in the near future
+
+[ ] Inquiry Suggestion [ ] Problem may be avoided until fixed
+
+[ ] Other______________ [ ] Problem is not time critical
+
+ [ ] Minor problem
+
+@end example
+
+
+Please provide a detailed description of the
+problem (Attachments including source code, example code,
+makefiles, possible solutions, and any other information
+describing the problem will be appreciated):
+
+
+
+
diff --git a/doc/relnotes/relnotes.texi b/doc/relnotes/relnotes.texi
new file mode 100644
index 0000000000..f4a2a24d36
--- /dev/null
+++ b/doc/relnotes/relnotes.texi
@@ -0,0 +1,116 @@
+\input ../texinfo/texinfo @c -*-texinfo-*-
+@c %**start of header
+@setfilename relnotes
+@syncodeindex vr fn
+@synindex ky cp
+@paragraphindent 0
+@c @smallbook
+@c %**end of header
+
+@c
+@c COPYRIGHT (c) 1988-1996.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+
+@c
+@c Master file
+@c
+
+@c Joel's Questions
+@c
+@c 1. Why does paragraphindent only impact makeinfo?
+@c 2. Why does paragraphindent show up in HTML?
+@c
+
+@include ../common/setup.texi
+
+@ignore
+@ifinfo
+@format
+START-INFO-DIR-ENTRY
+* RTEMS Release Notes: (relnotes). Release Notes
+END-INFO-DIR-ENTRY
+@end format
+@end ifinfo
+@end ignore
+
+@c variable substitution info:
+@c
+@c @set RTEMS-LANGUAGE C
+@c the language is @value{RTEMS-LANGUAGE}
+@c NOTE: don't use underscore in the name
+@c
+
+@c
+@c Title Page Stuff
+@c
+
+@set edition 4.0.0a
+@set update-date 25 April 1997
+@set update-month April 1997
+
+@c
+@c I don't really like having a short title page. --joel
+@c
+@c @shorttitlepage RTEMS Release Notes
+
+@setchapternewpage odd
+@settitle RTEMS Release Notes
+@titlepage
+@finalout
+
+@title RTEMS Release Notes
+@subtitle Edition @value{edition}, for RTEMS 4.0.0
+@sp 1
+@subtitle @value{update-month}
+@author On-Line Applications Research Corporation
+@page
+@include ../common/cpright.texi
+@end titlepage
+
+@c This prevents a black box from being printed on "overflow" lines.
+@c The alternative is to rework a sentence to avoid this problem.
+
+@include intro.texi
+@include install.texi
+@include status.texi
+@include probrep.texi
+
+@ifinfo
+@node Top, Introduction, (dir), (dir)
+@top relnotes
+
+This is the online version of the RTEMS Release Notes.
+
+@menu
+* Introduction::
+* Installation Procedure::
+* Development Environment Status::
+* RTEMS PROBLEM REPORT::
+* Command and Variable Index::
+* Concept Index::
+@end menu
+
+@end ifinfo
+@c
+@c
+@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here
+@c
+
+@node Command and Variable Index, Concept Index, RTEMS PROBLEM REPORT, Top
+@unnumbered Command and Variable Index
+
+There are currently no Command and Variable Index entries.
+
+@c @printindex fn
+
+@node Concept Index, , Command and Variable Index, Top
+@unnumbered Concept Index
+
+There are currently no Concept Index entries.
+@c @printindex cp
+
+@contents
+@bye
+
diff --git a/doc/relnotes/status.texi b/doc/relnotes/status.texi
new file mode 100644
index 0000000000..8a41b52b96
--- /dev/null
+++ b/doc/relnotes/status.texi
@@ -0,0 +1,258 @@
+@c
+@c COPYRIGHT (c) 1988-1996.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+
+@ifinfo
+@node Development Environment Status, Development Environment Status RTEMS Executive Status, Installation Procedure Installing RTEMS, Top
+@end ifinfo
+@chapter Development Environment Status
+@ifinfo
+@menu
+* Development Environment Status RTEMS Executive Status::
+* Development Environment Status Development Environment Status::
+* Development Environment Status Known Problems::
+@end menu
+@end ifinfo
+
+This chapter will describe the current status of
+release version @value{RTEMS-RELEASE} of the RTEMS Development Environment.
+
+@ifinfo
+@node Development Environment Status RTEMS Executive Status, Development Environment Status Development Environment Status, Development Environment Status, Development Environment Status
+@end ifinfo
+@section RTEMS Executive Status
+
+Release @value{RTEMS-RELEASE} of the RTEMS Executive contains support
+for both the classic RTEMS API based on the RTEID specification as well
+as support for POSIX threads and real-time extensions.
+
+The classic RTEMS API has the following managers based upon the RTEID
+specification:
+
+@itemize @bullet
+@item Task
+@item Initialization
+@item Clock
+@item Timer
+@item Interrupt
+@item Fatal Error
+@item Message
+@item Semaphore
+@item Event
+@item Signal
+@item Region
+@item Partition
+@item Dual Ported Memory
+@item I/O
+@item Multiprocessing
+@item Rate Monotonic
+@item User Extensions
+@end itemize
+
+RTEMS also has support for the following managers based upon the POSIX threads
+and real-time extensions:
+
+@itemize @bullet
+@item Thread
+@item Clock
+@item Key
+@item Condition Variable
+@item Mutex
+@item Signal
+@item Scheduler
+@end itemize
+
+This release of the C implementation supports the
+following processors and target boards:
+
+@itemize @bullet
+@item Motorola M68k family
+@itemize -
+@item DY-4 DMV152, SVME153
+@item Motorola IDP
+@item Motorola MVME135, MVME136
+@item Motorola MVME147, MVME147S
+@item Motorola MVME162
+@item EFI 68000 and 68332
+@item Generic 68302
+@item Generic 68360 and 68360 in companion mode with 68040
+@end itemize
+
+@item Intel i386 family
+@itemize -
+@item Force CPU386
+@item Intel i386ex eval board
+@item PC-AT i386 and above (go32)
+@end itemize
+
+@item Intel i960 family
+@itemize -
+@item Cyclone CVME960, CVME961
+@end itemize
+
+@item Hewlett Packard PA-RISC family
+@itemize -
+@item Processor Simulator
+@end itemize
+
+@item PowerPC
+@itemize -
+@item Papyrus (proprietary controller)
+@end itemize
+
+@item SPARC
+@itemize -
+@item ERC32 (space-hardened V7)
+@end itemize
+
+@item MIPS
+@itemize -
+@item P4000 with R4600 or R4650
+@end itemize
+
+@item AMD 29K
+@itemize -
+@item Portsw
+@end itemize
+
+@item UNIX
+@itemize -
+@item Hewlett Packard HPUX (PA-RISC)
+@item Sun Solaris 2.x (SPARC)
+@item Linux (i386)
+@end itemize
+
+@end itemize
+
+Support for the Cygnus NEWLIB Standard C Library is
+provided with this release which may be used on any of the RTEMS
+supported targets. The BSPs only provide support for console
+I/O only using this library. Support for the reentrancy
+capabilities of newlib is provided in the RTEMS distribution.
+
+@ifinfo
+@node Development Environment Status Development Environment Status, Development Environment Status Known Problems, Development Environment Status RTEMS Executive Status, Development Environment Status
+@end ifinfo
+@section Development Environment Status
+
+This section details the versions of the tools used
+to develop and maintain RTEMS @value{RTEMS-RELEASE}:
+
+@itemize @bullet
+@item Cross Tools
+@itemize -
+@item gcc - 2.7.2.2 with rtems patch
+@item binutils - 2.7 with rtems patch
+@item zip - 1.2.4
+@item make - 3.74
+@end itemize
+@end itemize
+
+
+@ifinfo
+@node Development Environment Status Known Problems, Executive Problems, Development Environment Status Development Environment Status, Development Environment Status
+@end ifinfo
+@section Known Problems
+@ifinfo
+@menu
+* Executive Problems::
+* Development Environment Problems::
+* RTEMS Problem Reporting::
+@end menu
+@end ifinfo
+
+Problems which are known to exist at the time of
+release are described in the following sections. These are
+provided as warnings to the user and where possible, workarounds
+are provided until the problem is corrected.
+
+@ifinfo
+@node Executive Problems, Development Environment Problems, Development Environment Status Known Problems, Development Environment Status Known Problems
+@end ifinfo
+@subsection Executive Problems
+
+There are no known bugs in the executive itself.
+
+@ifinfo
+@node Development Environment Problems, RTEMS Problem Reporting, Executive Problems, Development Environment Status Known Problems
+@end ifinfo
+@subsection Development Environment Problems
+
+There are no known major problems with the
+development environment.
+
+@ifinfo
+@node RTEMS Problem Reporting, RTEMS PROBLEM REPORT, Development Environment Problems, Development Environment Status Known Problems
+@end ifinfo
+@subsection RTEMS Problem Reporting
+
+A problem report is provided at the end of this
+document and may be copied by the RTEMS user. Please fill out
+the form completely to assure a speedy response to the problem.
+In filling out the problem report the following instructions
+apply:
+
+@table @code
+@item User Name and Address:
+The full name
+and mailing address of the customer or company where
+correspondence from RTEMS support personnel may be shipped.
+
+@item Contact Name:
+The name of the person with whom
+RTEMS support personnel will correspond with concerning the
+reported problem.
+
+@item Telephone Voice/FAX:
+The telephone numbers which
+will enable RTEMS support personnel to reach the designated
+contact name.
+
+@item Product/Version:
+The RTEMS product and the version that is currently in use.
+
+@item Target Processor/System:
+The processor and board type that is the target.
+
+@item Host Computer System:
+The manufacturer and model
+number of the system on which RTEMS has been installed.
+
+@item Host Operating System/Version:
+The operating system and version under which RTEMS has been installed.
+
+@c @item Report Type:
+@c Check the most appropriate description of the reported problem.
+
+@item Customer Impact:
+Indicate the severity of the impact of the reported problem.
+
+@item Detailed Description:
+A written description of the
+problem including the area of the RTEMS development environment
+where the problem is located and its behavior. Please feel free
+to provide source code listings, makefiles, possible solutions,
+and any other information describing the problem. This
+additional information may be submitted via email or anonymous
+ftp.
+
+Support, training, ports, and custom development are provided
+by On-Line Applications Research Corporation (OAR). Correspondence
+regarding any aspect of RTEMS should be addressed as follows
+(magnetic tapes should be marked: DO NOT X-RAY):
+@end table
+
+@example
+@group
+RTEMS
+On-Line Applications Research Corporation
+4910-L Corporate Drive
+Huntsville, AL 35805
+Voice: (205) 722-9985
+FAX: (205) 722-0985
+EMAIL: rtems@@OARcorp.com
+@end group
+@end example
+