[rtems commit] doc: Document new macros

Sebastian Huber sebh at rtems.org
Wed Apr 11 14:27:51 UTC 2012

Module:    rtems
Branch:    master
Commit:    ced0816218b0343a00fd08dcc67e759492c76aca
Changeset: http://git.rtems.org/rtems/commit/?id=ced0816218b0343a00fd08dcc67e759492c76aca

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Wed Apr 11 16:29:28 2012 +0200

doc: Document new macros


 doc/user/conf.t |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/doc/user/conf.t b/doc/user/conf.t
index d7f6809..7e403ca 100644
--- a/doc/user/conf.t
+++ b/doc/user/conf.t
@@ -2187,6 +2187,7 @@ need to control the size of the workspace very tightly because they just
 want to get the new software to run; later they can tune the workspace size
 as needed.
+ at findex rtems_resource_unlimited
 When the number of objects is not known ahead of time, RTEMS provides an
 auto-extending mode that can be enabled individually for each object
 type by using the macro @code{rtems_resource_unlimited}. This takes a value
@@ -2204,6 +2205,12 @@ allocation block of objects allocated. Here is an example of using
 #define CONFIGURE_MAXIMUM_TASKS rtems_resource_unlimited(5)
 @end example
+ at findex rtems_resource_is_unlimited
+ at findex rtems_resource_maximum_per_allocation
+Object maximum specifications can be evaluated with the
+ at code{rtems_resource_is_unlimited} and
+ at code{rtems_resource_maximum_per_allocation} macros.
 To ease the burden of developers who are porting new software RTEMS also
 provides the following macros:
 @itemize @bullet

More information about the vc mailing list