2008-08-21 Joel Sherrill <joel.sherrill@OARcorp.com>

	* bsp_howto/ata.t, bsp_howto/clock.t, bsp_howto/ide-ctrl.t,
	bsp_howto/nvmem.t, bsp_howto/shmsupp.t, user/datatypes.t, user/mp.t,
	user/userext.t: Eliminate all references to rtems_signedXX and
	rtems_unsignedXX.

3 files changed, 18 insertions, 22 deletions

diff --git a/doc/user/datatypes.t b/doc/user/datatypes.t
index 6f3e6e7ac7..e65695b483 100644
--- a/doc/user/datatypes.t
+++ b/doc/user/datatypes.t
@@ -194,29 +194,25 @@ that is expected to be used by the MPCI layer.
 type used to manage and manipulate RTEMS signal sets
 with the Signal Manager.
 
-@findex rtems_signed8
-@item @code{@value{DIRPREFIX}signed8} is the data
-type that corresponds to signed eight bit integers.
-This data type is defined by RTEMS in a manner that
+@findex int8_t
+@item @code{int8_t} is the C99 data type that corresponds to signed eight
+bit integers.  This data type is defined by RTEMS in a manner that
 ensures it is portable across different target processors.
 
-@findex rtems_signed16
-@item @code{@value{DIRPREFIX}signed16} is the data
-type that corresponds to signed sixteen bit integers.
-This data type is defined by RTEMS in a manner that
-ensures it is portable across different target processors.
+@findex int16_t
+@item @code{int16_t} is the C99 data type that corresponds to signed
+sixteen bit integers.  This data type is defined by RTEMS in a manner
+that ensures it is portable across different target processors.
 
-@findex rtems_signed32
-@item @code{@value{DIRPREFIX}signed32} is the data
-type that corresponds to signed thirty-two bit integers.
-This data type is defined by RTEMS in a manner that
-ensures it is portable across different target processors.
+@findex int32_t
+@item @code{int32_t} is the C99 data type that corresponds to signed
+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_signed64
-@item @code{@value{DIRPREFIX}signed64} is the data
-type that corresponds to signed sixty-four bit integers.
-This data type is defined by RTEMS in a manner that
-ensures it is portable across different target processors.
+@findex int64_t
+@item @code{int64_t} is the C99 data type that corresponds to signed
+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_single
 @item @code{@value{DIRPREFIX}single} is the RTEMS data
diff --git a/doc/user/mp.t b/doc/user/mp.t
index b1f16cbabf..693509af6d 100644
--- a/doc/user/mp.t
+++ b/doc/user/mp.t
@@ -410,7 +410,7 @@ following prototype:
 @example
 @group
 rtems_mpci_entry user_mpci_send_packet(
-  rtems_unsigned32       node,
+  uint32_t               node,
   rtems_packet_prefix  **packet
 );
 @end group
@@ -433,7 +433,7 @@ of the packet to avoid sending unnecessary data.  This is especially
 useful if the media connecting the nodes is relatively slow.
 
 The to_convert field of the MP_packet_prefix portion of the packet indicates
-how much of the packet (in @code{rtems_unsigned32}'s) may require
+how much of the packet (in @code{uint32_t}'s) may require
 conversion in a heterogeneous system.
 
 @subsection Supporting Heterogeneous Environments
diff --git a/doc/user/userext.t b/doc/user/userext.t
index 2bb4c81006..2a6fad440a 100644
--- a/doc/user/userext.t
+++ b/doc/user/userext.t
@@ -466,7 +466,7 @@ This extension should have a prototype similar to the following:
 rtems_extension user_fatal_error(
   Internal_errors_Source  the_source,
   rtems_boolean           is_internal,
-  rtems_unsigned32        the_error
+  uint32_t                the_error
 );
 @end example
 @end ifset