source: rtems-docs/c-user/config/index.rst @ a388de9

5
Last change on this file since a388de9 was a388de9, checked in by Sebastian Huber <sebastian.huber@…>, on 03/09/20 at 07:58:21

c-user: Move "Event Recording Configuration"

Update #3836.

  • Property mode set to 100644
File size: 6.8 KB
Line 
1.. SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
4
5.. index:: configuring a system
6.. _Configuring a System:
7
8Configuring a System
9********************
10
11.. toctree::
12
13    intro
14    general
15    classic-api
16    classic-init-task
17    posix-api
18    posix-init-thread
19    task-stack-alloc
20    msg-queue-buffer
21    filesystem
22    bdbuf
23    bsp-related
24    idle-task
25    scheduler-general
26    scheduler-clustered
27    device-driver
28    mpci
29    libpci
30    event-record
31
32.. _ConfigAda:
33
34Ada Configuration
35=================
36
37The GNU Ada runtime library (libgnarl) uses threads, mutexes, condition
38variables, and signals from the pthreads API.  It uses also thread-local storage
39for the Ada Task Control Block (ATCB).  From these resources only the threads
40need to be accounted for in the configuration.  You should include the Ada tasks
41in your setting of the :ref:`CONFIGURE_MAXIMUM_POSIX_THREADS` configuration
42option.
43
44Obsolete Configuration Options
45==============================
46
47.. index:: CONFIGURE_BDBUF_BUFFER_COUNT
48
49CONFIGURE_BDBUF_BUFFER_COUNT
50----------------------------
51
52This configuration option was introduced in RTEMS 4.7.0 and is obsolete since
53RTEMS 4.10.0.
54
55.. index:: CONFIGURE_BDBUF_BUFFER_SIZE
56
57CONFIGURE_BDBUF_BUFFER_SIZE
58---------------------------
59
60This configuration option was introduced in RTEMS 4.7.0 and is obsolete since
61RTEMS 4.10.0.
62
63.. index:: CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS
64
65CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS
66--------------------------------------
67
68This configuration option was introduced in RTEMS 4.9.0 and is obsolete since
69RTEMS 5.1.
70
71.. index:: CONFIGURE_ENABLE_GO
72
73CONFIGURE_ENABLE_GO
74-------------------
75
76This configuration option is obsolete since RTEMS 5.1.
77
78.. index:: CONFIGURE_GNAT_RTEMS
79
80CONFIGURE_GNAT_RTEMS
81--------------------
82
83This configuration option was present in all RTEMS versions since at 1997 and is
84obsolete since RTEMS 5.1.  See also :ref:`ConfigAda`.
85
86.. index:: CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
87
88CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
89-------------------------------------
90
91This configuration option is obsolete since RTEMS 5.1.
92
93.. index:: CONFIGURE_HAS_OWN_BDBUF_TABLE
94
95CONFIGURE_HAS_OWN_BDBUF_TABLE
96-----------------------------
97
98This configuration option was introduced in RTEMS 4.7.0 and is obsolete since
99RTEMS 4.10.0.
100
101.. index:: CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE
102
103CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE
104-------------------------------------
105
106This configuration option was present in all RTEMS versions since at least 1995
107and is obsolete since RTEMS 5.1.
108
109.. index:: CONFIGURE_HAS_OWN_INIT_TASK_TABLE
110
111.. _CONFIGURE_HAS_OWN_INIT_TASK_TABLE:
112
113CONFIGURE_HAS_OWN_INIT_TASK_TABLE
114---------------------------------
115
116This configuration option was present in all RTEMS versions since at least 1995
117and is obsolete since RTEMS 5.1.  If you used this configuration option or you
118think that there should be a way to configure more than one Classic API
119initialization task, then please ask on the :r:list:`users`.
120
121.. index:: CONFIGURE_HAS_OWN_MOUNT_TABLE
122
123CONFIGURE_HAS_OWN_MOUNT_TABLE
124-----------------------------
125
126This configuration option is obsolete since RTEMS 5.1.
127
128.. index:: CONFIGURE_HAS_OWN_MULTIPROCESSING_TABLE
129
130CONFIGURE_HAS_OWN_MULTIPROCESSING_TABLE
131---------------------------------------
132
133This configuration option is obsolete since RTEMS 5.1.
134
135.. index:: CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS
136
137CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS
138--------------------------------
139
140This configuration option was present in all RTEMS versions since at 1998 and is
141obsolete since RTEMS 5.1.  See also :ref:`CONFIGURE_MAXIMUM_FILE_DESCRIPTORS`.
142
143.. index:: CONFIGURE_MAXIMUM_ADA_TASKS
144
145CONFIGURE_MAXIMUM_ADA_TASKS
146---------------------------
147
148This configuration option was present in all RTEMS versions since at 1997 and is
149obsolete since RTEMS 5.1.  See also :ref:`ConfigAda`.
150
151.. index:: CONFIGURE_MAXIMUM_FAKE_ADA_TASKS
152
153CONFIGURE_MAXIMUM_FAKE_ADA_TASKS
154--------------------------------
155
156This configuration option was present in all RTEMS versions since at 1997 and is
157obsolete since RTEMS 5.1.  See also :ref:`ConfigAda`.
158
159.. index:: CONFIGURE_MAXIMUM_GO_CHANNELS
160
161CONFIGURE_MAXIMUM_GO_CHANNELS
162-----------------------------
163
164This configuration option is obsolete since RTEMS 5.1.
165
166.. index:: CONFIGURE_MAXIMUM_GOROUTINES
167
168CONFIGURE_MAXIMUM_GOROUTINES
169----------------------------
170
171This configuration option is obsolete since RTEMS 5.1.
172
173.. index:: CONFIGURE_MAXIMUM_MRSP_SEMAPHORES
174
175CONFIGURE_MAXIMUM_MRSP_SEMAPHORES
176---------------------------------
177
178This configuration option is obsolete since RTEMS 5.1.
179
180.. index:: CONFIGURE_NUMBER_OF_TERMIOS_PORTS
181
182CONFIGURE_NUMBER_OF_TERMIOS_PORTS
183---------------------------------
184
185This configuration option is obsolete since RTEMS 5.1.
186
187.. index:: CONFIGURE_MAXIMUM_POSIX_BARRIERS
188
189CONFIGURE_MAXIMUM_POSIX_BARRIERS
190--------------------------------
191
192This configuration option is obsolete since RTEMS 5.1.
193
194.. index:: CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
195
196CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
197-------------------------------------------
198
199This configuration option is obsolete since RTEMS 5.1.
200
201.. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS
202
203CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS
204-------------------------------
205
206This configuration option was introduced in RTEMS 4.10.0 and is obsolete since
207RTEMS 5.1.
208
209.. index:: CONFIGURE_MAXIMUM_POSIX_MUTEXES
210
211CONFIGURE_MAXIMUM_POSIX_MUTEXES
212-------------------------------
213
214This configuration option is obsolete since RTEMS 5.1.
215
216.. index:: CONFIGURE_MAXIMUM_POSIX_RWLOCKS
217
218CONFIGURE_MAXIMUM_POSIX_RWLOCKS
219-------------------------------
220
221This configuration option is obsolete since RTEMS 5.1.
222
223.. index:: CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
224
225CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
226---------------------------------
227
228This configuration option is obsolete since RTEMS 5.1.
229
230.. index:: CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
231
232.. _CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE:
233
234CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
235-----------------------------------------
236
237This configuration option was present in all RTEMS versions since at least 1995
238and is obsolete since RTEMS 5.1.  If you used this configuration option or you
239think that there should be a way to configure more than one POSIX initialization
240thread, then please ask on the  :r:list:`users`.
241
242.. index:: CONFIGURE_SMP_APPLICATION
243
244CONFIGURE_SMP_APPLICATION
245-------------------------
246
247This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
248RTEMS 5.1.
249
250.. index:: CONFIGURE_SMP_MAXIMUM_PROCESSORS
251
252CONFIGURE_SMP_MAXIMUM_PROCESSORS
253--------------------------------
254
255This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
256RTEMS 5.1.  See also :ref:`CONFIGURE_MAXIMUM_PROCESSORS`.
257
258.. index:: CONFIGURE_TERMIOS_DISABLED
259
260CONFIGURE_TERMIOS_DISABLED
261--------------------------
262
263This configuration option is obsolete since RTEMS 5.1.
Note: See TracBrowser for help on using the repository browser.