RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

corrected typos and changes LANGUAGE to RTEMS-LANGUAGE.

Browse Source
This commit is contained in:
Joel Sherrill
1997-07-31 18:45:58 +00:00
parent 03c8223b96
commit db91520362
23 changed files with 51 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/ada_user/ada_user.texi
View File

@@ -45,7 +45,7 @@ END-INFO-DIR-ENTRY
@set STRUCTURE record
@set ROUTINE subprogram
@set OR or
@c the language is @value{RTEMS-LANGUAGE}
@c the language is @value{LANGUAGE}
@c NOTE: don't use underscore in the name
@c

4
doc/develenv/develenv.texi
View File

@@ -39,8 +39,8 @@ END-INFO-DIR-ENTRY
@c variable substitution info:
@c
@c @set RTEMS-LANGUAGE C
@c the language is @value{RTEMS-LANGUAGE}
@c @set LANGUAGE C
@c the language is @value{LANGUAGE}
@c NOTE: don't use underscore in the name
@c

4
doc/develenv/direct.texi
View File

@@ -426,7 +426,7 @@ the supercore modules. Within the "score" directory the CPU
dependent modules are found.
The "cpu" directory contains a subdirectory for each
target CPU supported by the @value{RTEMS-RELEASE} release of the RTEMS
target CPU supported by the @value{RELEASE} release of the RTEMS
executive. Each processor directory contains the CPU dependent
code necessary to host RTEMS. The "no_cpu" directory provides a
starting point for developing a new port to an unsupported
@@ -459,7 +459,7 @@ processor family.
@c Tree 7 - C BSP Library
@c
Th "libbsp" directory provides all the BSPs provided with this
The "libbsp" directory provides all the BSPs provided with this
release of the RTEMS executive. The subdirectories are
divided, as discussed previously, based on specific processor
family, then further breaking down into specific target board

3
doc/develenv/sample.texi
View File

@@ -51,8 +51,7 @@ can be used to test locally developed board support packages and
device drivers.
The reader should be familiar with the terms used and
material presented in the RTEMS Applications User's Guide or
the RTEMS @value{RTEMS-LANGUAGE} Applications User's Guide.
material presented in the RTEMS Applications User's Guide.
@ifinfo
@node Sample Applications Hello World, Sample Applications Clock Tick, Sample Applications Introduction, Sample Applications

2
doc/do_docs
View File

@@ -5,7 +5,7 @@
basedir=$1
shift
manuals="develenv hppa1_1 i386 i960 m68k relnotes sparc user ka9q"
manuals="develenv hppa1_1 i386 i960 m68k relnotes powerpc sparc user ka9q"
# posix_test_plan manual left out until finished
# ada_user manual left out until bindings released

4
doc/new_chapters/posix_test_plan.texi
View File

@@ -39,8 +39,8 @@ END-INFO-DIR-ENTRY
@c variable substitution info:
@c
@c @set RTEMS-LANGUAGE C
@c the language is @value{RTEMS-LANGUAGE}
@c @set LANGUAGE C
@c the language is @value{LANGUAGE}
@c NOTE: don't use underscore in the name
@c

4
doc/posix_users/posix_test_plan.texi
View File

@@ -39,8 +39,8 @@ END-INFO-DIR-ENTRY
@c variable substitution info:
@c
@c @set RTEMS-LANGUAGE C
@c the language is @value{RTEMS-LANGUAGE}
@c @set LANGUAGE C
@c the language is @value{LANGUAGE}
@c NOTE: don't use underscore in the name
@c

6
doc/relnotes/install.texi
View File

@@ -46,9 +46,9 @@ Throughout the rest of this manual
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}.
ftp://ftp.OARcorp.com/oarcorp/rtems/@value{RELEASE}.
The archive files for RTEMS Release @value{RTEMS-RELEASE} are found
The archive files for RTEMS Release @value{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.
@@ -116,7 +116,7 @@ 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}.
components will be extracted into the subdirectory rtems-@value{RELEASE}.
To view the contents of a component without restoring any files,
use a command similar to the following:

2
doc/relnotes/intro.texi
View File

@@ -18,7 +18,7 @@
@end ifinfo
This document describes the contents, installation
procedure, and current status of Release @value{RTEMS-RELEASE} of the RTEMS
procedure, and current status of Release @value{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

4
doc/relnotes/relnotes.texi
View File

@@ -39,8 +39,8 @@ END-INFO-DIR-ENTRY
@c variable substitution info:
@c
@c @set RTEMS-LANGUAGE C
@c the language is @value{RTEMS-LANGUAGE}
@c @set LANGUAGE C
@c the language is @value{LANGUAGE}
@c NOTE: don't use underscore in the name
@c

6
doc/relnotes/status.texi
View File

@@ -19,14 +19,14 @@
@end ifinfo
This chapter will describe the current status of
release version @value{RTEMS-RELEASE} of the RTEMS Development Environment.
release version @value{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
Release @value{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.
@@ -140,7 +140,7 @@ capabilities of newlib is provided in the RTEMS distribution.
@section Development Environment Status
This section details the versions of the tools used
to develop and maintain RTEMS @value{RTEMS-RELEASE}:
to develop and maintain RTEMS @value{RELEASE}:
@itemize @bullet
@item Cross Tools

1
doc/rtems.html
View File

@@ -22,6 +22,7 @@
<LI><A HREF="c_m68k/Top.html">RTEMS Motorola MC68xxx Applications Supplement</A>
<LI><A HREF="HELP.html">RTEMS PowerPC Applications Supplement</A>
<LI><A HREF="c_sparc/Top.html">RTEMS SPARC Applications Supplement</A>
<LI><A HREF="c_powerpc/Top.html">RTEMS PowerPC Applications Supplement</A>
<LI><A HREF="c_hppa1_1/Top.html">RTEMS Hewlett Packard PA-RISC Applications Supplement</A>
<LI><A HREF="HELP.html">RTEMS UNIX Port Applications Supplement</A>
</MENU>

6
doc/supplements/i386/cputable.t
View File

@@ -40,7 +40,8 @@ is provided to allow RTEMS to interoperate effectively with the
BSP. The C structure definition is given here:
@example
struct cpu_configuration_table @{
@group
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*idle_task)( void );
@@ -53,7 +54,8 @@ struct cpu_configuration_table @{
unsigned32 interrupt_segment;
void *interrupt_vector_table;
@};
@} rtems_cpu_table;
@end group
@end example
@table @code

6
doc/supplements/i386/cputable.texi
View File

@@ -40,7 +40,8 @@ is provided to allow RTEMS to interoperate effectively with the
BSP. The C structure definition is given here:
@example
struct cpu_configuration_table @{
@group
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*idle_task)( void );
@@ -53,7 +54,8 @@ struct cpu_configuration_table @{
unsigned32 interrupt_segment;
void *interrupt_vector_table;
@};
@} rtems_cpu_table;
@end group
@end example
@table @code

6
doc/supplements/i960/cputable.t
View File

@@ -41,7 +41,8 @@ effectively with the BSP. The C structure definition is given
here:
@example
struct cpu_configuration_table @{
@group
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*postdriver_hook)( void );
@@ -56,7 +57,8 @@ struct cpu_configuration_table @{
i960ca_PRCB *Prcb;
#endif
@};
@} rtems_cpu_table;
@end group
@end example
The contents of the i960CA Processor Control Block

6
doc/supplements/i960/cputable.texi
View File

@@ -41,7 +41,8 @@ effectively with the BSP. The C structure definition is given
here:
@example
struct cpu_configuration_table @{
@group
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*postdriver_hook)( void );
@@ -56,7 +57,8 @@ struct cpu_configuration_table @{
i960ca_PRCB *Prcb;
#endif
@};
@} rtems_cpu_table;
@end group
@end example
The contents of the i960CA Processor Control Block

4
doc/supplements/m68k/cputable.t
View File

@@ -42,7 +42,7 @@ here:
@example
@group
struct cpu_configuration_table @{
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*postdriver_hook)( void );
@@ -55,7 +55,7 @@ struct cpu_configuration_table @{
/* end of fields required on all CPUs */
m68k_isr *interrupt_vector_table;
@};
@} rtems_cpu_table;
@end group
@end example

2
doc/supplements/sparc/bsp.t
View File

@@ -79,7 +79,7 @@ and this is to be utilized, then it should be enabled during the
reset application initialization code.
In addition to the requirements described in the
Board Support Packages chapter of the @value{RTEMS-LANGUAGE}
Board Support Packages chapter of the @value{LANGUAGE}
Applications User's Manual for the reset code
which is executed before the call to
rtems_initialize executive, the SPARC version has the following

2
doc/supplements/sparc/bsp.texi
View File

@@ -79,7 +79,7 @@ and this is to be utilized, then it should be enabled during the
reset application initialization code.
In addition to the requirements described in the
Board Support Packages chapter of the @value{RTEMS-LANGUAGE}
Board Support Packages chapter of the @value{LANGUAGE}
Applications User's Manual for the reset code
which is executed before the call to
rtems_initialize executive, the SPARC version has the following

2
doc/supplements/sparc/cpumodel.t
View File

@@ -141,7 +141,7 @@ The code required to enter low power mode is CPU model specific.
@end ifinfo
@section CPU Model Implementation Notes
The ERC is a custom SPARC V7 implementation based on the Cypress 601/602
The ERC32 is a custom SPARC V7 implementation based on the Cypress 601/602
chipset. This CPU has a number of on-board peripherals and was developed by
the European Space Agency to target space applications. RTEMS currently
provides support for the following peripherals:

2
doc/supplements/sparc/cpumodel.texi
View File

@@ -141,7 +141,7 @@ The code required to enter low power mode is CPU model specific.
@end ifinfo
@section CPU Model Implementation Notes
The ERC is a custom SPARC V7 implementation based on the Cypress 601/602
The ERC32 is a custom SPARC V7 implementation based on the Cypress 601/602
chipset. This CPU has a number of on-board peripherals and was developed by
the European Space Agency to target space applications. RTEMS currently
provides support for the following peripherals:

6
doc/supplements/sparc/cputable.t
View File

@@ -38,7 +38,8 @@ Information Table is given by the C structure definition is
shown below:
@example
struct cpu_configuration_table @{
@group
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*postdriver_hook)( void );
@@ -50,7 +51,8 @@ struct cpu_configuration_table @{
void (*stack_free_hook)( void* );
/* end of fields required on all CPUs */
@};
@} rtems_cpu_table;
@end group
@end example
@table @code

6
doc/supplements/sparc/cputable.texi
View File

@@ -38,7 +38,8 @@ Information Table is given by the C structure definition is
shown below:
@example
struct cpu_configuration_table @{
@group
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*postdriver_hook)( void );
@@ -50,7 +51,8 @@ struct cpu_configuration_table @{
void (*stack_free_hook)( void* );
/* end of fields required on all CPUs */
@};
@} rtems_cpu_table;
@end group
@end example
@table @code