Changeset 81ecc05b in rtems
- Timestamp:
- 05/28/00 18:21:16 (23 years ago)
- Branches:
- 4.10, 4.11, 4.8, 4.9, 5, master
- Children:
- 9fa28fbc
- Parents:
- f50c11b
- Location:
- doc/user
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user/conf.t
rf50c11b r81ecc05b 63 63 #define CONFIGURE_TICKS_PER_TIMESLICE 50 /* 50 milliseconds */ 64 64 65 #define CONFIGURE_MAXIMUM_TASKS 4 65 66 #define CONFIGURE_RTEMS_INIT_TASKS_TABLE 66 67 @end group … … 82 83 produced. 83 84 85 The user should be aware that the defaults are intentionally 86 set as low as possible. By default, no application resources 87 are configured. The @code{confdefs.h} file ensures that 88 at least one application tasks or thread is configured 89 and that at least one of the initialization task/thread 90 tables is configured. 91 92 The @code{confdefs.h} file estimates the amount of 93 memory required for the RTEMS Executive Workspace. This 94 estimate is only as accurate as the information given 95 to @code{confdefs.h} and may be either too high or too 96 low for a variety of reasons. Some of the reasons that 97 @code{confdefs.h} may reserve too much memory for RTEMS 98 are: 99 100 @itemize @bullet 101 @item All tasks/threads are assumed to be floating point. 102 @end itemize 103 104 Conversely, there are many more reasons, the resource 105 estimate could be too low: 106 107 @itemize @bullet 108 @item Task/thread stacks greater than minimum size must be 109 accounted for explicitly by developer. 110 111 @item Memory for messages is not included. 112 113 @item Device driver requirements are not included. 114 115 116 @item Network stack requirements are not included. 117 118 @item Requirements for add-on libraries are not included. 119 @end itemize 120 121 In general, @code{confdefs.h} is very accurate when given 122 enough information. However, it is quite easy to use 123 a library and not account for its resources. 124 84 125 The following subsection list all of the constants which can be 85 126 set by the user. … … 96 137 maximum number of files that can be concurrently open. Libio requires 97 138 a Classic RTEMS semaphore for each file descriptor as well as one 98 global one. The default value is 20 file descriptors. 139 global one. The default value is 3 file descriptors which is 140 enough to support standard input, output, and error output. 141 142 @findex CONFIGURE_TERMIOS_DISABLED 143 @item @code{CONFIGURE_TERMIOS_DISABLED} is defined if the 144 software implementing POSIX termios functionality is 145 not going to be used by this application. By default, this 146 is not defined and resources are reserved for the 147 termios functionality. 148 149 @findex CONFIGURE_NUMBER_OF_TERMIOS_PORTS 150 @item @code{CONFIGURE_NUMBER_OF_TERMIOS_PORTS} is set to the 151 number of ports using the termios functionality. Each 152 concurrently active termios port requires resources. 153 By default, this is set to 1 so a console port can be 154 used. 99 155 100 156 @findex CONFIGURE_HAS_OWN_MOUNT_TABLE … … 107 163 @code{rtems_filesystem_mount_table_t}. 108 164 109 @findex CONFIGURE_USE_MINIIMFS_AS_BASE_FILESYSTEM 110 @item @code{CONFIGURE_USE_MINIIMFS_AS_BASE_FILESYSTEM} is defined 111 if the application wishes to use a minimal functionality subset 112 of the In-Memory FileSystem (IMFS). The miniIMFS is comparable 165 @findex CONFIGURE_USE_IMFS_AS_BASE_FILESYSTEM 166 @item @code{CONFIGURE_USE_IMFS_AS_BASE_FILESYSTEM} is defined 167 if the application wishes to use the full functionality 168 IMFS. By default, the miniIMFS is used. The miniIMFS 169 is a minimal functionality subset of the In-Memory 170 FileSystem (IMFS). The miniIMFS is comparable 113 171 in functionality to the pseudo-filesystem name space provided 114 172 before RTEMS release 4.5.0. The miniIMFS supports 115 173 only directories and device nodes and is smaller in executable 116 code size than the full IMFS. By default, this is not 117 defined and the full functionality IMFS is used. 174 code size than the full IMFS. 118 175 119 176 @findex STACK_CHECKER_ON … … 142 199 usually set by the BSP but since this memory is allocated 143 200 from the RTEMS Ram Workspace, it must be accounted for. The 144 default for this field is RTEMS_MINIMUM_STACK_SIZE. 201 default for this field is RTEMS_MINIMUM_STACK_SIZE. [NOTE: 202 At this time, changing this constant does NOT change the 203 size of the interrupt stack, only the amount of memory 204 reserved for it.] 145 205 146 206 @findex CONFIGURE_EXECUTIVE_RAM_WORK_AREA … … 288 348 @item @code{CONFIGURE_MAXIMUM_TASKS} is the maximum number of 289 349 Classic API tasks that can be concurrently active. 290 The default for this field is 10.350 The default for this field is 0. 291 351 292 352 @findex CONFIGURE_MAXIMUM_TIMERS … … 416 476 @item @code{CONFIGURE_MAXIMUM_POSIX_THREADS} is the maximum number of 417 477 POSIX API threads that can be concurrently active. 418 The default is 10.478 The default is 0. 419 479 420 480 @findex CONFIGURE_MAXIMUM_POSIX_MUTEXES … … 504 564 is the maximum number of 505 565 ITRON API tasks that can be concurrently active. 506 The default is 10.566 The default is 0. 507 567 508 568 @findex CONFIGURE_MAXIMUM_ITRON_SEMAPHORES -
doc/user/example.texi
rf50c11b r81ecc05b 75 75 #define CONFIGURE_TEST_NEEDS_CLOCK_DRIVER /* for time services */ 76 76 77 #define CONFIGURE_MAXIMUM_TASKS 2 78 77 79 #define CONFIGURE_INIT_TASK_NAME rtems_build_name( 'E', 'X', 'A', 'M' ) 78 80 #define CONFIGURE_RTEMS_INIT_TASKS_TABLE
Note: See TracChangeset
for help on using the changeset viewer.