1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
|
.. SPDX-License-Identifier: CC-BY-SA-4.0
.. Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
.. index:: configuring a system
.. _Configuring a System:
Configuring a System
********************
.. toctree::
intro
general
classic-api
classic-init-task
posix-api
posix-init-thread
task-stack-alloc
msg-queue-buffer
filesystem
bdbuf
bsp-related
idle-task
scheduler-general
scheduler-clustered
device-driver
mpci
PCI Library Configuration
=========================
This section defines the system configuration parameters supported by
``rtems/confdefs.h`` related to configuring the PCI Library for RTEMS.
The PCI Library startup behaviour can be configured in four different ways
depending on how ``CONFIGURE_PCI_CONFIG_LIB`` is defined:
.. index:: PCI_LIB_AUTO
``PCI_LIB_AUTO``
Used to enable the PCI auto configuration software. PCI will be automatically
probed, PCI buses enumerated, all devices and bridges will be initialized
using Plug & Play software routines. The PCI device tree will be populated
based on the PCI devices found in the system, PCI devices will be configured
by allocating address region resources automatically in PCI space according
to the BSP or host bridge driver set up.
.. index:: PCI_LIB_READ
``PCI_LIB_READ``
Used to enable the PCI read configuration software. The current PCI
configuration is read to create the RAM representation (the PCI device tree)
of the PCI devices present. PCI devices are assumed to already have been
initialized and PCI buses enumerated, it is therefore required that a BIOS or
a boot loader has set up configuration space prior to booting into RTEMS.
.. index:: PCI_LIB_STATIC
``PCI_LIB_STATIC``
Used to enable the PCI static configuration software. The user provides a PCI
tree with information how all PCI devices are to be configured at compile
time by linking in a custom ``struct pci_bus pci_hb`` tree. The static PCI
library will not probe PCI for devices, instead it will assume that all
devices defined by the user are present, it will enumerate the PCI buses and
configure all PCI devices in static configuration accordingly. Since probe
and allocation software is not needed the startup is faster, has smaller
footprint and does not require dynamic memory allocation.
.. index:: PCI_LIB_PERIPHERAL
``PCI_LIB_PERIPHERAL``
Used to enable the PCI peripheral configuration. It is similar to
``PCI_LIB_STATIC``, but it will never write the configuration to the PCI
devices since PCI peripherals are not allowed to access PCI configuration
space.
Note that selecting ``PCI_LIB_STATIC`` or ``PCI_LIB_PERIPHERAL`` but not
defining ``pci_hb`` will reuslt in link errors. Note also that in these modes
Plug & Play is not performed.
Event Recording Configuration
=============================
.. index:: CONFIGURE_RECORD_EXTENSIONS_ENABLED
.. _CONFIGURE_RECORD_EXTENSIONS_ENABLED:
CONFIGURE_RECORD_EXTENSIONS_ENABLED
-----------------------------------
CONSTANT:
``CONFIGURE_RECORD_EXTENSIONS_ENABLED``
DATA TYPE:
Boolean feature macro.
RANGE:
Defined or undefined.
DEFAULT VALUE:
This is not defined by default.
DESCRIPTION:
If defined and :ref:`CONFIGURE_RECORD_PER_PROCESSOR_ITEMS
<CONFIGURE_RECORD_PER_PROCESSOR_ITEMS>` is also defined properly, then the
record extensions are enabled.
NOTES:
The record extensions capture thread create, start, restart, delete,
switch, begin, exitted and terminate events.
.. index:: CONFIGURE_RECORD_PER_PROCESSOR_ITEMS
.. _CONFIGURE_RECORD_PER_PROCESSOR_ITEMS:
CONFIGURE_RECORD_PER_PROCESSOR_ITEMS
------------------------------------
CONSTANT:
``CONFIGURE_RECORD_PER_PROCESSOR_ITEMS``
DATA TYPE:
Unsigned integer (``unsigned int``).
RANGE:
A power of two greater than or equal to 16.
DEFAULT VALUE:
This is not defined by default.
DESCRIPTION:
If defined, then a record item buffer of the specified item count is
statically allocated for each configured processor
(:ref:`CONFIGURE_MAXIMUM_PROCESSORS <CONFIGURE_MAXIMUM_PROCESSORS>`).
NOTES:
None.
.. _ConfigAda:
Ada Configuration
=================
The GNU Ada runtime library (libgnarl) uses threads, mutexes, condition
variables, and signals from the pthreads API. It uses also thread-local storage
for the Ada Task Control Block (ATCB). From these resources only the threads
need to be accounted for in the configuration. You should include the Ada tasks
in your setting of the :ref:`CONFIGURE_MAXIMUM_POSIX_THREADS` configuration
option.
Obsolete Configuration Options
==============================
.. index:: CONFIGURE_BDBUF_BUFFER_COUNT
CONFIGURE_BDBUF_BUFFER_COUNT
----------------------------
This configuration option was introduced in RTEMS 4.7.0 and is obsolete since
RTEMS 4.10.0.
.. index:: CONFIGURE_BDBUF_BUFFER_SIZE
CONFIGURE_BDBUF_BUFFER_SIZE
---------------------------
This configuration option was introduced in RTEMS 4.7.0 and is obsolete since
RTEMS 4.10.0.
.. index:: CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS
CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS
--------------------------------------
This configuration option was introduced in RTEMS 4.9.0 and is obsolete since
RTEMS 5.1.
.. index:: CONFIGURE_ENABLE_GO
CONFIGURE_ENABLE_GO
-------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_GNAT_RTEMS
CONFIGURE_GNAT_RTEMS
--------------------
This configuration option was present in all RTEMS versions since at 1997 and is
obsolete since RTEMS 5.1. See also :ref:`ConfigAda`.
.. index:: CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
-------------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_HAS_OWN_BDBUF_TABLE
CONFIGURE_HAS_OWN_BDBUF_TABLE
-----------------------------
This configuration option was introduced in RTEMS 4.7.0 and is obsolete since
RTEMS 4.10.0.
.. index:: CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE
CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE
-------------------------------------
This configuration option was present in all RTEMS versions since at least 1995
and is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_HAS_OWN_INIT_TASK_TABLE
.. _CONFIGURE_HAS_OWN_INIT_TASK_TABLE:
CONFIGURE_HAS_OWN_INIT_TASK_TABLE
---------------------------------
This configuration option was present in all RTEMS versions since at least 1995
and is obsolete since RTEMS 5.1. If you used this configuration option or you
think that there should be a way to configure more than one Classic API
initialization task, then please ask on the :r:list:`users`.
.. index:: CONFIGURE_HAS_OWN_MOUNT_TABLE
CONFIGURE_HAS_OWN_MOUNT_TABLE
-----------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_HAS_OWN_MULTIPROCESSING_TABLE
CONFIGURE_HAS_OWN_MULTIPROCESSING_TABLE
---------------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS
CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS
--------------------------------
This configuration option was present in all RTEMS versions since at 1998 and is
obsolete since RTEMS 5.1. See also :ref:`CONFIGURE_MAXIMUM_FILE_DESCRIPTORS`.
.. index:: CONFIGURE_MAXIMUM_ADA_TASKS
CONFIGURE_MAXIMUM_ADA_TASKS
---------------------------
This configuration option was present in all RTEMS versions since at 1997 and is
obsolete since RTEMS 5.1. See also :ref:`ConfigAda`.
.. index:: CONFIGURE_MAXIMUM_FAKE_ADA_TASKS
CONFIGURE_MAXIMUM_FAKE_ADA_TASKS
--------------------------------
This configuration option was present in all RTEMS versions since at 1997 and is
obsolete since RTEMS 5.1. See also :ref:`ConfigAda`.
.. index:: CONFIGURE_MAXIMUM_GO_CHANNELS
CONFIGURE_MAXIMUM_GO_CHANNELS
-----------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_GOROUTINES
CONFIGURE_MAXIMUM_GOROUTINES
----------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_MRSP_SEMAPHORES
CONFIGURE_MAXIMUM_MRSP_SEMAPHORES
---------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_NUMBER_OF_TERMIOS_PORTS
CONFIGURE_NUMBER_OF_TERMIOS_PORTS
---------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_POSIX_BARRIERS
CONFIGURE_MAXIMUM_POSIX_BARRIERS
--------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
-------------------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS
CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS
-------------------------------
This configuration option was introduced in RTEMS 4.10.0 and is obsolete since
RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_POSIX_MUTEXES
CONFIGURE_MAXIMUM_POSIX_MUTEXES
-------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_POSIX_RWLOCKS
CONFIGURE_MAXIMUM_POSIX_RWLOCKS
-------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
---------------------------------
This configuration option is obsolete since RTEMS 5.1.
.. index:: CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
.. _CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE:
CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
-----------------------------------------
This configuration option was present in all RTEMS versions since at least 1995
and is obsolete since RTEMS 5.1. If you used this configuration option or you
think that there should be a way to configure more than one POSIX initialization
thread, then please ask on the :r:list:`users`.
.. index:: CONFIGURE_SMP_APPLICATION
CONFIGURE_SMP_APPLICATION
-------------------------
This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
RTEMS 5.1.
.. index:: CONFIGURE_SMP_MAXIMUM_PROCESSORS
CONFIGURE_SMP_MAXIMUM_PROCESSORS
--------------------------------
This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
RTEMS 5.1. See also :ref:`CONFIGURE_MAXIMUM_PROCESSORS`.
.. index:: CONFIGURE_TERMIOS_DISABLED
CONFIGURE_TERMIOS_DISABLED
--------------------------
This configuration option is obsolete since RTEMS 5.1.
|