2007-11-28 Glenn Humphrey <glenn.humphrey@OARcorp.com>

* user/barrier.t, user/clock.t, user/concepts.t, user/conf.t,
	user/datatypes.t, user/dpmem.t, user/fatal.t, user/init.t, user/mp.t,
	user/msg.t, user/part.t, user/region.t, user/rtmon.t, user/sem.t,
	user/task.t, user/timer.t: Corrected various errors in the
	documentation.
This commit is contained in:
Glenn Humphrey
2007-11-28 16:23:59 +00:00
parent 29925d9971
commit ae10dbd9b6
17 changed files with 275 additions and 524 deletions

View File

@@ -280,30 +280,6 @@ return type for an RTEMS Timer Service Routine.
the entry point to an RTEMS TSR. It is equivalent to the
entry point of the function implementing the TSR.
@findex rtems_unsigned8
@item @code{@value{DIRPREFIX}unsigned8} is the data
type that corresponds to unsigned eight bit integers.
This data type is defined by RTEMS in a manner that
ensures it is portable across different target processors.
@findex rtems_unsigned16
@item @code{@value{DIRPREFIX}unsigned16} is the data
type that corresponds to unsigned sixteen bit integers.
This data type is defined by RTEMS in a manner that
ensures it is portable across different target processors.
@findex rtems_unsigned32
@item @code{@value{DIRPREFIX}unsigned32} is the data
type that corresponds to unsigned thirty-two bit integers.
This data type is defined by RTEMS in a manner that
ensures it is portable across different target processors.
@findex rtems_unsigned64
@item @code{@value{DIRPREFIX}unsigned64} is the data
type that corresponds to unsigned sixty-four bit integers.
This data type is defined by RTEMS in a manner that
ensures it is portable across different target processors.
@findex rtems_vector_number
@item @code{@value{DIRPREFIX}vector_number} is the data
type used to manage and manipulate interrupt vector numbers.