diff options
Diffstat (limited to '')
-rw-r--r-- | doc/FAQ/FAQ.texi | 3 | ||||
-rw-r--r-- | doc/FAQ/Makefile.am | 2 | ||||
-rw-r--r-- | doc/FAQ/basic.t | 6 | ||||
-rw-r--r-- | doc/FAQ/bsp.t | 4 | ||||
-rw-r--r-- | doc/FAQ/build45.t | 10 | ||||
-rw-r--r-- | doc/FAQ/concepts.t | 2 | ||||
-rw-r--r-- | doc/FAQ/debug.t | 2 | ||||
-rw-r--r-- | doc/FAQ/embeddedinfo.t | 2 | ||||
-rw-r--r-- | doc/FAQ/endoftime.t | 6 | ||||
-rw-r--r-- | doc/FAQ/freesw.t | 2 | ||||
-rw-r--r-- | doc/FAQ/hwdebugaids.t | 2 | ||||
-rw-r--r-- | doc/FAQ/projects.t | 2 | ||||
-rw-r--r-- | doc/FAQ/stamp-vti | 4 | ||||
-rw-r--r-- | doc/FAQ/tools.t | 2 | ||||
-rw-r--r-- | doc/FAQ/version.texi | 4 |
15 files changed, 27 insertions, 26 deletions
diff --git a/doc/FAQ/FAQ.texi b/doc/FAQ/FAQ.texi index 9d55971472..4157db66c2 100644 --- a/doc/FAQ/FAQ.texi +++ b/doc/FAQ/FAQ.texi @@ -1,13 +1,14 @@ \input texinfo @c -*-texinfo-*- @c %**start of header @setfilename FAQ +@setcontentsaftertitlepage @syncodeindex vr fn @synindex ky cp @paragraphindent 0 @c %**end of header @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/Makefile.am b/doc/FAQ/Makefile.am index 8021d7d649..b7b3f60c8e 100644 --- a/doc/FAQ/Makefile.am +++ b/doc/FAQ/Makefile.am @@ -1,5 +1,5 @@ # -# COPYRIGHT (c) 1988-1999. +# COPYRIGHT (c) 1988-2002. # On-Line Applications Research Corporation (OAR). # All rights reserved. # diff --git a/doc/FAQ/basic.t b/doc/FAQ/basic.t index 11e984ee24..41547d5ef7 100644 --- a/doc/FAQ/basic.t +++ b/doc/FAQ/basic.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c @@ -13,7 +13,7 @@ did it come from, why is it, what is it, when should you use it, etc.? @section What does RTEMS stand for? -RTEMS is an anacronym for the Real-Time Executive for Multiprocessor +RTEMS is an an acronym for the Real-Time Executive for Multiprocessor Systems. Initially RTEMS stood for the Real-Time Executive for Missile Systems @@ -28,7 +28,7 @@ remained with the "M" meaning Military. RTEMS is a real-time executive which provides a high performance environment for embedded military applications including many features. The following is just a short list of the features -avilable in RTEMS. If you are interested in something that +available in RTEMS. If you are interested in something that is not on this list, please contact the RTEMS Team. Features are being added continuously. diff --git a/doc/FAQ/bsp.t b/doc/FAQ/bsp.t index 1e8488aab6..f4305be9ba 100644 --- a/doc/FAQ/bsp.t +++ b/doc/FAQ/bsp.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c @@ -29,7 +29,7 @@ EXCEPT hello world and the timing tests. The timer driver is a benchmark timer and is needed for the tmtests (timing tests). Sometimes you will see a shmsupp directory which is for shared memory multiprocessing systems. The network driver and real-time clock drivers are optional -and not reqired by any RTEMS tests. +and not required by any RTEMS tests. diff --git a/doc/FAQ/build45.t b/doc/FAQ/build45.t index 32660e7d41..d209a8f43b 100644 --- a/doc/FAQ/build45.t +++ b/doc/FAQ/build45.t @@ -125,7 +125,7 @@ prefix, eg. i386-rtems-gcc, m68k-rtems-ld are target tools. Host tools are supposed not to be prefixed. e.g.: cc, ld, gcc etc. -If using OARCorp's rpms for the toolchain, simply prepend: +If using OAR Corporation's rpms for the toolchain, simply prepend @code{/opt/rtems/bin} to @code{$PATH}. @subsection Can I build RTEMS Canadian Cross? @@ -247,7 +247,7 @@ templates when implementing BSPs or porting RTEMS to new CPUs. @subsection What is the bare-BSP? At the time being RTEMS is build per BSP, with all support files being build -separately for each BSP. This can become unhandy when using several similiar +separately for each BSP. This can become unhandy when using several similar but not identical boards (e.g. a PC with different peripherial cards plugged in), because this in general requires to implement a BSP for each setup. The bare BSP is a general, setup independent BSP which can be used when @@ -301,7 +301,7 @@ To remove them before importing, run ./bootstrap -c @end example -from the toplevel directory of the source tree (XXX ref sec-bootstrap). +from the toplevel directory of the source tree (cf. @ref{./bootstrap}). @subsection ./bootstrap @@ -309,7 +309,7 @@ from the toplevel directory of the source tree (XXX ref sec-bootstrap). @code{bootstrap} is a simple shell script which automatically generates all auto* generated files within RTEMS's source tree (Other packages use the name @code{autogen.sh} for similar scripts). You will need to have autoconf, -automake and further underlaying packages installed to apply it. +automake and further underlying packages installed to apply it. It typically should be applied when having: @@ -343,4 +343,4 @@ will let automake take care about dependencies between auto* generated files. I.e. auto* generated files will get automatically updated. Configuring RTEMS in maintainer-mode will require to have autoconf, automake -and underlaying tools installed (Cf. @ref{Required Tools}). +and underlying tools installed (Cf. @ref{Required Tools}). diff --git a/doc/FAQ/concepts.t b/doc/FAQ/concepts.t index 1ad0bdf657..87fa454ab0 100644 --- a/doc/FAQ/concepts.t +++ b/doc/FAQ/concepts.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/debug.t b/doc/FAQ/debug.t index 11acaa253d..08f3b991fc 100644 --- a/doc/FAQ/debug.t +++ b/doc/FAQ/debug.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/embeddedinfo.t b/doc/FAQ/embeddedinfo.t index f592db07de..d153093b3a 100644 --- a/doc/FAQ/embeddedinfo.t +++ b/doc/FAQ/embeddedinfo.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/endoftime.t b/doc/FAQ/endoftime.t index 5f6d3592ca..9ba5436aef 100644 --- a/doc/FAQ/endoftime.t +++ b/doc/FAQ/endoftime.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c @@ -42,7 +42,7 @@ to either the existence of the board or RTEMS are past 2000. The starting year (epoch) for RTEMS is 1988. Thus, @itemize @bullet -@item Chip year values 88-99 are interpreted as years 1988-1999. +@item Chip year values 88-99 are interpreted as years 1988-2002. @item Chip year values 00-87 are interpreted as years 2000-2087. @end itemize @@ -84,7 +84,7 @@ to correctly report dates after 2099, then it is possible for the Each embedded system could be impacted by a variety of date/time representation issues. Even whether a particular date/time -repsentation issue impacts a system is questionable. A system +representation issue impacts a system is questionable. A system using only the RTEMS Classic API is not impacted by the date/time representation issues in POSIX. A system not using date/time at all is not impacted by any of these issues. Also diff --git a/doc/FAQ/freesw.t b/doc/FAQ/freesw.t index ec524b61a6..acf580d328 100644 --- a/doc/FAQ/freesw.t +++ b/doc/FAQ/freesw.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/hwdebugaids.t b/doc/FAQ/hwdebugaids.t index 765ba6d921..5283e43251 100644 --- a/doc/FAQ/hwdebugaids.t +++ b/doc/FAQ/hwdebugaids.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/projects.t b/doc/FAQ/projects.t index 5bd7043207..bf1abaa974 100644 --- a/doc/FAQ/projects.t +++ b/doc/FAQ/projects.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/stamp-vti b/doc/FAQ/stamp-vti index b81c670e11..91e60ee8f2 100644 --- a/doc/FAQ/stamp-vti +++ b/doc/FAQ/stamp-vti @@ -1,3 +1,3 @@ -@set UPDATED 14 June 2000 +@set UPDATED 17 January 2002 @set EDITION 1 -@set VERSION 4.5.0-beta3 +@set VERSION 4.5.1-pre3 diff --git a/doc/FAQ/tools.t b/doc/FAQ/tools.t index 011f4945a6..d917f9d461 100644 --- a/doc/FAQ/tools.t +++ b/doc/FAQ/tools.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-1999. +@c COPYRIGHT (c) 1988-2002. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c diff --git a/doc/FAQ/version.texi b/doc/FAQ/version.texi index b81c670e11..91e60ee8f2 100644 --- a/doc/FAQ/version.texi +++ b/doc/FAQ/version.texi @@ -1,3 +1,3 @@ -@set UPDATED 14 June 2000 +@set UPDATED 17 January 2002 @set EDITION 1 -@set VERSION 4.5.0-beta3 +@set VERSION 4.5.1-pre3 |