<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 4/10/2013 8:33 AM, Gedare Bloom
wrote:<br>
</div>
<blockquote
cite="mid:CAC82fA0w7di=--F9=iv=O18VY8rVkruXB9RkweCQ=7YJU1+XXA@mail.gmail.com"
type="cite">
<p>Looks good. Later we might want to specify actual ranges with
valid min and max or set notation of possible values.</p>
</blockquote>
Agreed. <br>
<br>
It looks like Sebastian addressed most, if not all, of what was on
my<br>
review list. <br>
<br>
I am sure there are still improvements to be made but this should<br>
be committed.<br>
<br>
--joel<br>
<blockquote
cite="mid:CAC82fA0w7di=--F9=iv=O18VY8rVkruXB9RkweCQ=7YJU1+XXA@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Apr 10, 2013 8:44 AM, "Sebastian
Huber" <<a moz-do-not-send="true"
href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-brains.de</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
---<br>
doc/user/conf.t | 366
+++++++++++++++++++++++++------------------------------<br>
1 files changed, 166 insertions(+), 200 deletions(-)<br>
<br>
diff --git a/doc/user/conf.t b/doc/user/conf.t<br>
index a1aabd4..1e52dcf 100644<br>
--- a/doc/user/conf.t<br>
+++ b/doc/user/conf.t<br>
@@ -71,7 +71,7 @@ expect that all systems can be easily
configured using the<br>
avoid internal RTEMS configuration changes impacting
applications.<br>
<br>
@c<br>
-@c === Philospohy ===<br>
+@c === Philosophy ===<br>
@c<br>
@section Default Value Selection Philosophy<br>
<br>
@@ -95,19 +95,16 @@ from the RTEMS Workspace.<br>
<br>
The @code{<rtems/confdefs.h>} mechanism calculates the
size of the RTEMS<br>
Workspace automatically. It assumes that all tasks are
floating point and<br>
-that all will be allocated the mininum stack space. This
calculation<br>
+that all will be allocated the minimum stack space. This
calculation<br>
includes the amount of memory that will be allocated for
internal use<br>
by RTEMS. The automatic calculation may underestimate the
workspace<br>
size truly needed by the application, in which case one can
use the<br>
@code{CONFIGURE_MEMORY_OVERHEAD} macro to add a value to the
estimate. See<br>
@ref{Configuring a System Specify Memory Overhead} for more
details.<br>
<br>
-@c XXX - ************* REMOVE ME *************<br>
-@c The starting address of the RTEMS Workspace is determined<br>
-@c by the BSP and must be aligned on at least a four-byte
boundary.<br>
-@c Failure to properly align the workspace will result in the<br>
-@c @code{@value{DIRPREFIX}fatal_error_occurred} directive
being invoked<br>
-@c with the @code{@value{RPREFIX}INVALID_ADDRESS} error code.<br>
+The memory area for the RTEMS Workspace is determined by the
BSP. In case the<br>
+RTEMS Workspace is too large for the available memory, then a
fatal run-time<br>
+error occurs and the system terminates.<br>
<br>
The file @code{<rtems/confdefs.h>} will calculate the
value of the<br>
@code{work_space_size} parameter of the Configuration Table.
There<br>
@@ -147,9 +144,8 @@ automatic estimates of space required will
in general change when:<br>
@item the target processor is changed.<br>
@end itemize<br>
<br>
-Failure to provide enough space in the RTEMS Workspace will
result in<br>
-the @code{@value{DIRPREFIX}fatal_error_occurred} directive
being invoked<br>
-with the appropriate error code.<br>
+Failure to provide enough space in the RTEMS Workspace may
result in fatal<br>
+run-time errors terminating the system.<br>
<br>
@c<br>
@c === Potential Issues ===<br>
@@ -211,7 +207,7 @@ fifty (50) milliseconds is as follows:<br>
#define CONFIGURE_MAXIMUM_MESSAGE_QUEUES 1<br>
<br>
#define CONFIGURE_MESSAGE_BUFFER_MEMORY \<br>
- CONFIGURE_MESSAGE_BUFFERS_FOR_QUEUE( 10, sizeof(struct
USER_MESSAGE))<br>
+ CONFIGURE_MESSAGE_BUFFERS_FOR_QUEUE(20, sizeof(struct
USER_MESSAGE))<br>
<br>
#define CONFIGURE_INIT<br>
#include <rtems/confdefs.h><br>
@@ -279,7 +275,8 @@ other things, the application implicitly
used the following defaults:<br>
@item All unspecified types of communications and
synchronization objects<br>
in the Classic and POSIX Threads API have maximums of zero
(0).<br>
<br>
-@item The filesystem will be the default filesystem which
only supports device nodes.<br>
+@item The filesystem will be the default filesystem which is
the In-Memory File<br>
+System (IMFS).<br>
<br>
@item The application will have the default number of
priority levels.<br>
<br>
@@ -426,10 +423,10 @@ pool of memory for both RTEMS and
application memory allocations.<br>
@code{CONFIGURE_OBJECTS_ALLOCATION_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-undefined or positive<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
If not defined and @code{CONFIGURE_OBJECTS_UNLIMITED} is
defined, the<br>
@@ -474,10 +471,10 @@ parameters supported by
@code{<rtems/confdefs.h>}.<br>
@code{CONFIGURE_MAXIMUM_TASKS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -491,7 +488,7 @@ Tasks that can be concurrently active.<br>
@subheading NOTES:<br>
This object class can be configured in unlimited allocation
mode.<br>
<br>
-This calculations for the required memory in the RTEMS
Workspace<br>
+The calculations for the required memory in the RTEMS
Workspace<br>
for tasks assume that each task has a minimum stack size and<br>
has floating point support enabled. The configuration
parameter<br>
@code{CONFIGURE_EXTRA_TASK_STACKS} is used to specify task
stack<br>
@@ -553,10 +550,10 @@ and this can save significant memory in
a low RAM system.<br>
@code{CONFIGURE_MAXIMUM_TIMERS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -582,10 +579,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_SEMAPHORES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -611,10 +608,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_MESSAGE_QUEUES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -640,10 +637,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_BARRIERS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -669,10 +666,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_PERIODS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -698,10 +695,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_PARTITIONS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -727,10 +724,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_REGIONS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -756,10 +753,10 @@ None.<br>
@code{CONFIGURE_MAXIMUM_PORTS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -785,10 +782,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_USER_EXTENSIONS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -863,10 +860,10 @@ any initialization tasks or threads.<br>
@code{CONFIGURE_INIT_TASK_ENTRY_POINT}<br>
<br>
@item DATA TYPE:<br>
-rtems_task_entry<br>
+Task entry function pointer (@code{rtems_task_entry}).<br>
<br>
@item RANGE:<br>
-valid method pointer<br>
+Valid task entry function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
By default the value is @code{Init}.<br>
@@ -879,7 +876,7 @@ name) of the single initialization task
defined by the Classic API<br>
Initialization Tasks Table.<br>
<br>
@subheading NOTES:<br>
-The user must implement the method @code{Init} or the method
name provided<br>
+The user must implement the function @code{Init} or the
function name provided<br>
in this configuration parameter.<br>
<br>
@c<br>
@@ -894,10 +891,10 @@ in this configuration parameter.<br>
@code{CONFIGURE_INIT_TASK_NAME}<br>
<br>
@item DATA TYPE:<br>
-rtems_name<br>
+RTEMS Name (@code{rtems_name}).<br>
<br>
@item RANGE:<br>
-any value<br>
+Any value.<br>
<br>
@item DEFAULT VALUE:<br>
By default the value is @code{rtems_build_name( 'U', 'I',
'1', ' ' )}.<br>
@@ -923,10 +920,10 @@ None.<br>
@code{CONFIGURE_INIT_TASK_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
By default value is the configured minimum stack size.<br>
@@ -955,10 +952,10 @@ for more information about
@code{CONFIGURE_EXTRA_TASK_STACKS}.<br>
@code{CONFIGURE_INIT_TASK_PRIORITY}<br>
<br>
@item DATA TYPE:<br>
-rtems_task_priority<br>
+RTEMS Task Priority (@code{rtems_task_priority}).<br>
<br>
@item RANGE:<br>
-1 to CONFIGURE_MAXIMUM_PRIORITY<br>
+One (1) to CONFIGURE_MAXIMUM_PRIORITY.<br>
<br>
@item DEFAULT VALUE:<br>
By default the value is one (1) which is the highest priority
in the<br>
@@ -986,10 +983,10 @@ None.<br>
<br>
<br>
@item DATA TYPE:<br>
-rtems_attributes<br>
+RTEMS Attributes (@code{rtems_attribute}).<br>
<br>
@item RANGE:<br>
-valid task attribute sets<br>
+Valid task attribute sets.<br>
<br>
@item DEFAULT VALUE:<br>
By default the tvalue is @code{RTEMS_DEFAULT_ATTRIBUTES}.<br>
@@ -1015,10 +1012,10 @@ None.<br>
@code{CONFIGURE_INIT_TASK_INITIAL_MODES}<br>
<br>
@item DATA TYPE:<br>
-rtems_mode<br>
+RTEMS Mode (@code{rtems_mode}).<br>
<br>
@item RANGE:<br>
-valid task mode sets<br>
+Valid task mode sets.<br>
<br>
@item DEFAULT VALUE:<br>
By default the value is @code{RTEMS_NO_PREEMPT}.<br>
@@ -1045,10 +1042,10 @@ None.<br>
@code{CONFIGURE_INIT_TASK_ARGUMENTS}<br>
<br>
@item DATA TYPE:<br>
-rtems_task_argument<br>
+RTEMS Task Argument (@code{rtems_task_argument}).<br>
<br>
@item RANGE:<br>
-valid rtems_task_argument values<br>
+Complete range of the type.<br>
<br>
@item DEFAULT VALUE:<br>
By default the value is 0.<br>
@@ -1114,10 +1111,10 @@ is enabled at configure time using the
@code{--enable-posix} option.<br>
@code{CONFIGURE_MAXIMUM_POSIX_THREADS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1158,10 +1155,10 @@ All POSIX threads have floating point
enabled.<br>
@code{CONFIGURE_MAXIMUM_POSIX_MUTEXES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1187,10 +1184,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1216,10 +1213,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_KEYS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1247,10 +1244,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_TIMERS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1276,10 +1273,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1305,10 +1302,10 @@ None.<br>
@code{CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1336,7 +1333,7 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
greater than or equal to
@code{CONFIGURE_MAXIMUM_POSIX_MESSAGES_QUEUES}<br>
@@ -1369,10 +1366,10 @@ greater than or equal to
@code{CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES}.<br>
@code{CONFIGURE_MAXIMUM_POSIX_SEMAPHORES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1398,10 +1395,10 @@ None.<br>
@code{CONFIGURE_MAXIMUM_POSIX_BARRIERS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1427,10 +1424,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_SPINLOCKS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1456,10 +1453,10 @@ This object class can be configured in
unlimited allocation mode.<br>
@code{CONFIGURE_MAXIMUM_POSIX_RWLOCKS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default for this field is 0.<br>
@@ -1536,10 +1533,10 @@ any initialization tasks or threads.<br>
@code{CONFIGURE_POSIX_INIT_THREAD_ENTRY_POINT}<br>
<br>
@item DATA TYPE:<br>
-void *(*entry_point)(void *)<br>
+POSIX thread function pointer (@code{void
*(*entry_point)(void *)}).<br>
<br>
@item RANGE:<br>
-valid method pointer<br>
+Undefined or a valid POSIX thread function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
By default the value is @code{POSIX_Init}.<br>
@@ -1552,7 +1549,7 @@ By default the value is
@code{POSIX_Init}.<br>
the POSIX API Initialization Threads Table.<br>
<br>
@subheading NOTES:<br>
-The user must implement the method @code{POSIX_Init} or the
method name<br>
+The user must implement the function @code{POSIX_Init} or the
function name<br>
provided in this configuration parameter.<br>
<br>
@c<br>
@@ -1567,10 +1564,10 @@ provided in this configuration
parameter.<br>
@code{CONFIGURE_POSIX_INIT_THREAD_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
By default value is twice the configured minimum stack size.<br>
@@ -1685,10 +1682,10 @@ run out of RTEMS Workspace.<br>
@code{CONFIGURE_MICROSECONDS_PER_TICK}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-non-zero positive values<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
When not defined, the clock tick quantum is configured to be
10,000<br>
@@ -1735,10 +1732,10 @@ a clock tick quantum.<br>
<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-non-zero positive values<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
If unspecified, this parameter defaults to fifty (50).<br>
@@ -1767,7 +1764,7 @@ driver is not configured.<br>
@code{CONFIGURE_MAXIMUM_PRIORITY}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint8_t}).<br>
<br>
@item RANGE:<br>
Valid values for this configuration parameter must be one (1)
less than<br>
@@ -1815,10 +1812,10 @@ to sixteen (16) can reduce memory
usage by about three (3) kilobytes.<br>
@code{CONFIGURE_MINIMUM_TASK_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-non-zero positive integer<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
When not defined by the application, this is set to the
recommended<br>
@@ -1856,10 +1853,10 @@ risk of stack overflow without
performing analysis on actual consumption.<br>
@code{CONFIGURE_INTERRUPT_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-non-zero positive integer<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
If not specified, the interrupt stack will be of minimum
size.<br>
@@ -1895,10 +1892,10 @@ from the RTEMS Workspace would be
welcomed by the RTEMS Project.<br>
@code{CONFIGURE_EXTRA_TASK_STACKS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-Undefined or positive<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
When this is not defined, the default value is 0.<br>
@@ -1997,7 +1994,7 @@ overhead to each context switch.<br>
@code{CONFIGURE_INITIAL_EXTENSIONS}<br>
<br>
@item DATA TYPE:<br>
-List of @code{rtems_extensions_table} entries<br>
+List of user extension initializers
(@code{rtems_extensions_table}).<br>
<br>
@item RANGE:<br>
Undefined or a list of one or more user extensions.<br>
@@ -2037,10 +2034,10 @@ so that stack overflows are detected
in hardware.<br>
@code{CONFIGURE_TASK_STACK_ALLOCATOR_INIT}<br>
<br>
@item DATA TYPE:<br>
-method pointer<br>
+Function pointer.<br>
<br>
@item RANGE:<br>
-NULL or valid pointer to a method<br>
+Undefined, NULL or valid function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
The default value for this field is NULL which indicates that<br>
@@ -2076,14 +2073,14 @@ A correctly configured system must
configure the following to be consistent:<br>
@code{CONFIGURE_TASK_STACK_ALLOCATOR}<br>
<br>
@item DATA TYPE:<br>
-method pointer<br>
+Function pointer.<br>
<br>
@item RANGE:<br>
-NULL or valid method pointer<br>
+Undefined or valid function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
-The default value for this field is NULL which indicates that<br>
-task stacks will be allocated from the RTEMS Workspace.<br>
+The default value for this field is
@code{_Workspace_Allocate} which indicates<br>
+that task stacks will be allocated from the RTEMS Workspace.<br>
<br>
@end table<br>
<br>
@@ -2113,13 +2110,13 @@ A correctly configured system must
configure the following to be consistent:<br>
@code{CONFIGURE_TASK_STACK_DEALLOCATOR}<br>
<br>
@item DATA TYPE:<br>
-method pointer<br>
+Function pointer.<br>
<br>
@item RANGE:<br>
-undefined or valid pointer<br>
+Undefined or valid function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
-The default value for this field is NULL which indicates that<br>
+The default value for this field is @code{_Workspace_Free}
which indicates that<br>
task stacks will be allocated from the RTEMS Workspace.<br>
<br>
@end table<br>
@@ -2155,16 +2152,16 @@ the amount of memory reserved for
Classic API Message Buffers.<br>
<br>
@table @b<br>
@item CONSTANT:<br>
-@code{CONFIGURE_MESSAGE_BUFFERS_FOR_QUEUE}<br>
+@code{CONFIGURE_MESSAGE_BUFFERS_FOR_QUEUE(max_messages,
size_per)}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
-This macro is only used as input to<br>
+None.<br>
<br>
@end table<br>
<br>
@@ -2257,10 +2254,10 @@ and providing work-arounds when the
memory estimated by<br>
@code{CONFIGURE_MEMORY_OVERHEAD}<br>
<br>
@item DATA TYPE:<br>
-undefined or integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default value is 0.<br>
@@ -2307,36 +2304,6 @@ is providing their own complete set of
configuration tables.<br>
None.<br>
<br>
@c<br>
-@c === CONFIGURE_EXECUTIVE_RAM_WORK_AREA ===<br>
-@c<br>
-@subsection Specify Location of RTEMS Workspace<br>
-<br>
-@findex CONFIGURE_EXECUTIVE_RAM_WORK_AREA<br>
-<br>
-@table @b<br>
-@item CONSTANT:<br>
-@code{CONFIGURE_EXECUTIVE_RAM_WORK_AREA}<br>
-<br>
-@item DATA TYPE:<br>
-pointer<br>
-<br>
-@item RANGE:<br>
-NULL or valid pointer<br>
-<br>
-@item DEFAULT VALUE:<br>
-By default, this value is not defined indicating that the BSP
is to determine<br>
-the location of the RTEMS Workspace.<br>
-<br>
-@end table<br>
-<br>
-@subheading DESCRIPTION:<br>
-This configuration parameter is the base address of the RTEMS
Workspace.<br>
-<br>
-@subheading NOTES:<br>
-The BSP is responsible for setting this address. It is highly
unlikely<br>
-that an application could do this portably and reliably.<br>
-<br>
-@c<br>
@c === C Library Support Configuration ===<br>
@c<br>
@section C Library Support Configuration<br>
@@ -2389,10 +2356,10 @@ None.<br>
@code{CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-Zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
If not defined, the default value is either zero (0) or three
if<br>
@@ -2403,15 +2370,11 @@ I/O streams on @code{/dev/console}.<br>
@end table<br>
<br>
@subheading DESCRIPTION:<br>
-This configuration parameter is set to the maximum number of
files that<br>
-can be concurrently open.<br>
+This configuration parameter is set to the maximum number of
file like objects<br>
+that can be concurrently open.<br>
<br>
@subheading NOTES:<br>
-In addition to the actual file descriptor data structures,
the RTEMS<br>
-Libio Support library requires a Classic API semaphore for
each file<br>
-descriptor as well as one to manage the set. Thus this
configuration<br>
-parameter implicitly impacts the configured number of Classic
API<br>
-semaphores configured for the application.<br>
+None.<br>
<br>
@c<br>
@c === CONFIGURE_TERMIOS_DISABLED ===<br>
@@ -2457,13 +2420,13 @@ device driver.<br>
@code{CONFIGURE_NUMBER_OF_TERMIOS_PORTS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer.<br>
<br>
@item RANGE:<br>
-zero or positive integer<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
-By default, this is set to 1 so a console port can be used.<br>
+By default, this is set to one (1) so a console port can be
used.<br>
<br>
@end table<br>
<br>
@@ -2539,7 +2502,6 @@ Boolean feature macro.<br>
Defined or undefined.<br>
<br>
@item DEFAULT VALUE:<br>
-<br>
This value is not defined by default. If no other root file
system<br>
configuration parameters are specified, the IMFS will be used
as the<br>
root file system.<br>
@@ -2600,6 +2562,7 @@ space provided before RTEMS release
4.5.0.<br>
<br>
@table @b<br>
@item CONSTANT:<br>
+@code{CONFIGURE_APPLICATION_DISABLE_FILESYSTEM}<br>
<br>
@item DATA TYPE:<br>
Boolean feature macro.<br>
@@ -2615,13 +2578,13 @@ root file system.<br>
@end table<br>
<br>
@subheading DESCRIPTION:<br>
-@code{CONFIGURE_APPLICATION_DISABLE_FILESYSTEM}<br>
-<br>
-@subheading NOTES:<br>
This configuration parameter is defined if the application
dose not<br>
intend to use any kind of filesystem support. This include
the device<br>
infrastructure necessary to support @code{printf()}.<br>
<br>
+@subheading NOTES:<br>
+None.<br>
+<br>
@c<br>
@c === BSP Specific Settings ===<br>
@c<br>
@@ -2678,7 +2641,7 @@ Boolean feature macro.<br>
Defined or undefined.<br>
<br>
@item DEFAULT VALUE:<br>
-This configuration is undefined by default.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2706,13 +2669,13 @@ knows how it allocates memory to the C
Program Heap.<br>
@code{BSP_IDLE_TASK_BODY}<br>
<br>
@item DATA TYPE:<br>
-Pointer to method.<br>
+Function pointer.<br>
<br>
@item RANGE:<br>
-Null or pointer to method.<br>
+Undefined or valid function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
-This is not defined by default.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2738,13 +2701,13 @@ components off to save power during
extended periods of no task activity<br>
@code{BSP_IDLE_TASK_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-undefined or positive integer<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
-This is not defined by default.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2779,13 +2742,13 @@ The order of precedence for
configuring the IDLE task stack size is:<br>
@code{BSP_INITIAL_EXTENSION}<br>
<br>
@item DATA TYPE:<br>
-List of @code{rtems_extensions_table} entries<br>
+List of user extension initializers
(@code{rtems_extensions_table}).<br>
<br>
@item RANGE:<br>
-Undefined or a list of one or more user extensions.<br>
+Undefined or a list of user extension initializers.<br>
<br>
@item DEFAULT VALUE:<br>
-This value is not defined by default.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2809,10 +2772,13 @@ None.<br>
@code{BSP_INTERRUPT_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2836,26 +2802,25 @@ None.<br>
@code{BSP_MAXIMUM_DEVICES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
-By default, this is not defined.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@subheading DESCRIPTION:<br>
If @code{BSP_MAXIMUM_DEVICES} is defined by the BSP and<br>
@code{CONFIGURE_MAXIMUM_DEVICES} is not defined by the
application,<br>
-then this BSP specific maximum device count will be used.
This option<br>
-is specific to the device file system (devFS) and should not
be confused<br>
-with the @code{CONFIGURE_MAXIMUM_DRIVERS} option.<br>
+then this BSP specific maximum device count will be used.<br>
<br>
@subheading NOTES:<br>
-This parameter only impacts the devFS and thus<br>
-is only used by @code{<rtems/confdefs.h>} when<br>
+This option is specific to the device file system (devFS) and
should not be<br>
+confused with the @code{CONFIGURE_MAXIMUM_DRIVERS} option.
This parameter only<br>
+impacts the devFS and thus is only used by
@code{<rtems/confdefs.h>} when<br>
@code{CONFIGURE_USE_DEVFS_AS_BASE_FILESYSTEM} is specified.<br>
<br>
@c<br>
@@ -2876,7 +2841,7 @@ Boolean feature macro.<br>
Defined or undefined.<br>
<br>
@item DEFAULT VALUE:<br>
-This is not defined by default.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2901,13 +2866,13 @@ necessary for RTEMS but is often
assumed by support libraries.<br>
@code{CONFIGURE_BSP_PREREQUISITE_DRIVERS}<br>
<br>
@item DATA TYPE:<br>
-array of device drivers<br>
+List of device driver initializers
(@code{rtems_driver_address_table}).<br>
<br>
@item RANGE:<br>
-Undefined or array of device drivers<br>
+Undefined or array of device drivers.<br>
<br>
@item DEFAULT VALUE:<br>
-By default, this is not defined.<br>
+This option is BSP specific.<br>
<br>
@end table<br>
<br>
@@ -2944,10 +2909,10 @@ supported by
@code{<rtems/confdefs.h>}.<br>
@code{CONFIGURE_IDLE_TASK_BODY}<br>
<br>
@item DATA TYPE:<br>
-method pointer.<br>
+Function pointer.<br>
<br>
@item RANGE:<br>
-Undefined or method pointer.<br>
+Undefined or valid function pointer.<br>
<br>
@item DEFAULT VALUE:<br>
By default, this is not defined.<br>
@@ -2955,7 +2920,7 @@ By default, this is not defined.<br>
@end table<br>
<br>
@subheading DESCRIPTION:<br>
-@code{CONFIGURE_IDLE_TASK_BODY} is set to the method name
corresponding<br>
+@code{CONFIGURE_IDLE_TASK_BODY} is set to the function name
corresponding<br>
to the application specific IDLE thread body. If not
specified, the<br>
BSP or RTEMS default IDLE thread body will be used.<br>
<br>
@@ -2974,10 +2939,10 @@ None.<br>
@code{CONFIGURE_IDLE_TASK_STACK_SIZE}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{size_t}).<br>
<br>
@item RANGE:<br>
-undefined or positive<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
If not specified, the IDLE task will have a stack of the
configured<br>
@@ -3380,7 +3345,7 @@ Note that network device drivers are not
configured in the Device Driver Table.<br>
@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE}<br>
<br>
@item DATA TYPE:<br>
-Array of device drivers.<br>
+List of device driver initializers
(@code{rtems_driver_address_table}).<br>
<br>
@item RANGE:<br>
Undefined or array of device drivers.<br>
@@ -3413,10 +3378,10 @@ It is expected that there the
application would only rarely need to do this.<br>
@code{CONFIGURE_MAXIMUM_DRIVERS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
By default, this is set to the number of device drivers
configured<br>
@@ -3448,10 +3413,10 @@ are statically installed.<br>
@code{CONFIGURE_MAXIMUM_DEVICES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-undefined or positive integer.<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
Unless @code{BSP_MAXIMUM_DEVICES} is set by the BSP, the
default value<br>
@@ -3462,11 +3427,12 @@ value specified by the BSP.<br>
<br>
@subheading DESCRIPTION:<br>
@code{CONFIGURE_MAXIMUM_DEVICES} is defined to the number of<br>
-individual devices that may be registered in the system.<br>
+individual devices that may be registered in the device file
system (devFS).<br>
<br>
@subheading NOTES:<br>
-This parameter only impacts the devFS and thus<br>
-is only used by @code{<rtems/confdefs.h>} when<br>
+This option is specific to the device file system (devFS) and
should not be<br>
+confused with the @code{CONFIGURE_MAXIMUM_DRIVERS} option.
This parameter only<br>
+impacts the devFS and thus is only used by
@code{<rtems/confdefs.h>} when<br>
@code{CONFIGURE_USE_DEVFS_AS_BASE_FILESYSTEM} is specified.<br>
<br>
@c<br>
@@ -3478,7 +3444,7 @@ is only used by
@code{<rtems/confdefs.h>} when<br>
<br>
@table @b<br>
@item CONSTANT:<br>
-@item @code{CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER}<br>
+@code{CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER}<br>
<br>
@item DATA TYPE:<br>
Boolean feature macro.<br>
@@ -3919,10 +3885,10 @@ This has no impact unless RTEMS was
configured and built using the<br>
@code{CONFIGURE_MP_NODE_NUMBER}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-positive integer<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
If not defined, it is set to @code{NODE_NUMBER} which is
assumed to be<br>
@@ -3953,10 +3919,10 @@ differently based upon their node
number.<br>
@code{CONFIGURE_MP_MAXIMUM_NODES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-positive<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default is two (2).<br>
@@ -3982,10 +3948,10 @@ None.<br>
@code{CONFIGURE_MP_MAXIMUM_GLOBAL_OBJECTS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-positive<br>
+Positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default is 32.<br>
@@ -4012,10 +3978,10 @@ created with the @code{RTEMS_GLOBAL}
attribute.<br>
@code{CONFIGURE_MP_MAXIMUM_PROXIES}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-undefined or positive<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
The default is 32.<br>
@@ -4159,10 +4125,10 @@ run-time.<br>
@code{CONFIGURE_MAXIMUM_ADA_TASKS}<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-undefined or positive<br>
+Undefined or positive.<br>
<br>
@item DEFAULT VALUE:<br>
By default, when @code{CONFIGURE_GNAT_RTEMS} is defined, this
is set to 20.<br>
@@ -4188,10 +4154,10 @@ None.<br>
@findex CONFIGURE_MAXIMUM_FAKE_ADA_TASKS<br>
<br>
@item DATA TYPE:<br>
-integer<br>
+Unsigned integer (@code{uint32_t}).<br>
<br>
@item RANGE:<br>
-zero or positive<br>
+Zero or positive.<br>
<br>
@item DEFAULT VALUE:<br>
By default, this is undefined which implies zero (0) @i{fake}
Ada Tasks.<br>
--<br>
1.7.7<br>
<br>
_______________________________________________<br>
rtems-devel mailing list<br>
<a moz-do-not-send="true" href="mailto:rtems-devel@rtems.org">rtems-devel@rtems.org</a><br>
<a moz-do-not-send="true"
href="http://www.rtems.org/mailman/listinfo/rtems-devel"
target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
</blockquote>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Joel Sherrill, Ph.D. Director of Research & Development
<a class="moz-txt-link-abbreviated" href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985 </pre>
</body>
</html>