From ced0816218b0343a00fd08dcc67e759492c76aca Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 11 Apr 2012 16:29:28 +0200 Subject: doc: Document new macros --- doc/user/conf.t | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc') diff --git a/doc/user/conf.t b/doc/user/conf.t index d7f68097ee..7e403cab95 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. +@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 +@findex rtems_resource_is_unlimited +@findex rtems_resource_maximum_per_allocation +Object maximum specifications can be evaluated with the +@code{rtems_resource_is_unlimited} and +@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 -- cgit v1.2.3