From 94fb30d46d5af625519ba5dc94d57dd546442be7 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Thu, 7 Aug 2008 13:44:58 +0000 Subject: 2008-08-07 Joel Sherrill * user/datatypes.t: Add rtems_name. Add comment about rtems_task_argument changing from simple unsigned thirty two bit integer to being derived from a C99 uintptr_t in 4.8 and newer. --- doc/user/datatypes.t | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'doc/user/datatypes.t') diff --git a/doc/user/datatypes.t b/doc/user/datatypes.t index da2c26b14e..6f3e6e7ac7 100644 --- a/doc/user/datatypes.t +++ b/doc/user/datatypes.t @@ -169,6 +169,13 @@ the entry point to the send packet routine for an MPCI implementation. @item @code{@value{DIRPREFIX}mpci_table} is the data structure containing the configuration information for an MPCI. +@findex rtems_name +@item @code{@value{DIRPREFIX}name} is the data type used to +contain the name of a Classic API object. It is an unsigned +thirty-two bit integer which can be treated as a numeric +value or initialized using @code{@value{DIRPREFIX}build_name} to +contain four ASCII characters. + @findex rtems_option @item @code{@value{DIRPREFIX}option} is the data type used to specify which behavioral options the caller desires. @@ -224,7 +231,11 @@ RTEMS Task. @findex rtems_task_argument @item @code{@value{DIRPREFIX}task_argument} is the data -type for the argument passed to each RTEMS task. +type for the argument passed to each RTEMS task. In RTEMS 4.7 +and older, this is an unsigned thirty-two bit integer. In +RTEMS 4.8 and newer, this is based upon the C99 type @code{uintptr_t} +which is guaranteed to be an integer large enough to hold a +pointer on the target architecture. @findex rtems_task_begin_extension @item @code{@value{DIRPREFIX}task_begin_extension} is the -- cgit v1.2.3