[rtems-docs commit] c-user: Add obsolete configuration options section
Sebastian Huber
sebh at rtems.org
Mon Oct 9 06:05:43 UTC 2017
Module: rtems-docs
Branch: master
Commit: d8f7bdc003f560e8b3b002e18a56c18692d737d8
Changeset: http://git.rtems.org/rtems-docs/commit/?id=d8f7bdc003f560e8b3b002e18a56c18692d737d8
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Fri Oct 6 14:29:00 2017 +0200
c-user: Add obsolete configuration options section
Update #2493.
Update #3112.
Update #3113.
Update #3114.
Update #3115.
Update #3116.
---
c-user/configuring_a_system.rst | 252 ++++++++++++++--------------------------
1 file changed, 88 insertions(+), 164 deletions(-)
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
index bed95cf..01904a1 100644
--- a/c-user/configuring_a_system.rst
+++ b/c-user/configuring_a_system.rst
@@ -1182,62 +1182,6 @@ NOTES:
All POSIX threads have floating point enabled.
-.. COMMENT: XXX - Add xref to CONFIGURE_MAXIMUM_TASKS.
-
-.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_MUTEXES ===
-
-.. _Specify Maximum POSIX API Mutexes:
-
-Specify Maximum POSIX API Mutexes
----------------------------------
-.. index:: CONFIGURE_MAXIMUM_POSIX_MUTEXES
-
-CONSTANT:
- ``CONFIGURE_MAXIMUM_POSIX_MUTEXES``
-
-DATA TYPE:
- Unsigned integer (``uint32_t``).
-
-RANGE:
- Zero or positive.
-
-DEFAULT VALUE:
- The default value is 0.
-
-DESCRIPTION:
- ``CONFIGURE_MAXIMUM_POSIX_MUTEXES`` is the maximum number of POSIX API
- Mutexes that can be concurrently active.
-
-NOTES:
- This object class can be configured in unlimited allocation mode.
-
-.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES ===
-
-.. _Specify Maximum POSIX API Condition Variables:
-
-Specify Maximum POSIX API Condition Variables
----------------------------------------------
-.. index:: CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
-
-CONSTANT:
- ``CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES``
-
-DATA TYPE:
- Unsigned integer (``uint32_t``).
-
-RANGE:
- Zero or positive.
-
-DEFAULT VALUE:
- The default value is 0.
-
-DESCRIPTION:
- ``CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES`` is the maximum number of
- POSIX API Condition Variables that can be concurrently active.
-
-NOTES:
- This object class can be configured in unlimited allocation mode.
-
.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_KEYS ===
.. _Specify Maximum POSIX API Keys:
@@ -1348,114 +1292,6 @@ DESCRIPTION:
NOTES:
This object class can be configured in unlimited allocation mode.
-.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_SEMAPHORES ===
-
-.. _Specify Maximum POSIX API Semaphores:
-
-Specify Maximum POSIX API Semaphores
-------------------------------------
-.. index:: CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
-
-CONSTANT:
- ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES``
-
-DATA TYPE:
- Unsigned integer (``uint32_t``).
-
-RANGE:
- Zero or positive.
-
-DEFAULT VALUE:
- The default value is 0.
-
-DESCRIPTION:
- ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES`` is the maximum number of POSIX API
- Semaphores that can be concurrently active.
-
-NOTES:
- None.
-
-.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_BARRIERS ===
-
-.. _Specify Maximum POSIX API Barriers:
-
-Specify Maximum POSIX API Barriers
-----------------------------------
-.. index:: CONFIGURE_MAXIMUM_POSIX_BARRIERS
-
-CONSTANT:
- ``CONFIGURE_MAXIMUM_POSIX_BARRIERS``
-
-DATA TYPE:
- Unsigned integer (``uint32_t``).
-
-RANGE:
- Zero or positive.
-
-DEFAULT VALUE:
- The default value is 0.
-
-DESCRIPTION:
- ``CONFIGURE_MAXIMUM_POSIX_BARRIERS`` is the maximum number of POSIX API
- Barriers that can be concurrently active.
-
-NOTES:
- This object class can be configured in unlimited allocation mode.
-
-.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_SPINLOCKS ===
-
-.. _Specify Maximum POSIX API Spinlocks:
-
-Specify Maximum POSIX API Spinlocks
------------------------------------
-.. index:: CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
-
-CONSTANT:
- ``CONFIGURE_MAXIMUM_POSIX_SPINLOCKS``
-
-DATA TYPE:
- Unsigned integer (``uint32_t``).
-
-RANGE:
- Zero or positive.
-
-DEFAULT VALUE:
- The default value is 0.
-
-DESCRIPTION:
- ``CONFIGURE_MAXIMUM_POSIX_SPINLOCKS`` is the maximum number of POSIX API
- Spinlocks that can be concurrently active.
-
-NOTES:
- This object class can be configured in unlimited allocation mode.
-
-.. COMMENT: === CONFIGURE_MAXIMUM_POSIX_RWLOCKS ===
-
-.. _Specify Maximum POSIX API Read/Write Locks:
-
-Specify Maximum POSIX API Read/Write Locks
-------------------------------------------
-.. index:: CONFIGURE_MAXIMUM_POSIX_RWLOCKS
-
-CONSTANT:
- ``CONFIGURE_MAXIMUM_POSIX_RWLOCKS``
-
-DATA TYPE:
- Unsigned integer (``uint32_t``).
-
-RANGE:
- Zero or positive.
-
-DEFAULT VALUE:
- The default value is 0.
-
-DESCRIPTION:
- ``CONFIGURE_MAXIMUM_POSIX_RWLOCKS`` is the maximum number of POSIX API
- Read/Write Locks that can be concurrently active.
-
-NOTES:
- This object class can be configured in unlimited allocation mode.
-
.. COMMENT: === POSIX Initialization Threads Table Configuration ===
POSIX Initialization Threads Table Configuration
@@ -5087,3 +4923,91 @@ DESCRIPTION:
NOTES:
The Go language support is experimental
+
+Obsolete Configuration Options
+==============================
+
+CONFIGURE_BDBUF_BUFFER_COUNT
+----------------------------
+.. index:: CONFIGURE_BDBUF_BUFFER_COUNT
+
+This configuration option was introduced in RTEMS 4.7 and is obsolete since
+RTEMS 4.10.
+
+CONFIGURE_BDBUF_BUFFER_SIZE
+---------------------------
+.. index:: CONFIGURE_BDBUF_BUFFER_SIZE
+
+This configuration option was introduced in RTEMS 4.7 and is obsolete since
+RTEMS 4.10.
+
+CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS
+--------------------------------------
+.. index:: CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS
+
+This configuration option was introduced in RTEMS 4.9 and is obsolete since
+RTEMS 4.12.
+
+CONFIGURE_HAS_OWN_BDBUF_TABLE
+-----------------------------
+.. index:: CONFIGURE_HAS_OWN_BDBUF_TABLE
+
+This configuration option was introduced in RTEMS 4.7 and is obsolete since
+RTEMS 4.10.
+
+CONFIGURE_MAXIMUM_POSIX_BARRIERS
+--------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_BARRIERS
+
+This configuration option is obsolete since RTEMS 4.12.
+
+CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
+-------------------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_CONDITION_VARIABLES
+
+This configuration option is obsolete since RTEMS 4.12.
+
+CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS
+-------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUE_DESCRIPTORS
+
+This configuration option was introduced in RTEMS 4.10 and is obsolete since
+RTEMS 4.12.
+
+CONFIGURE_MAXIMUM_POSIX_MUTEXES
+-------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_MUTEXES
+
+This configuration option is obsolete since RTEMS 4.12.
+
+CONFIGURE_MAXIMUM_POSIX_RWLOCKS
+-------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_RWLOCKS
+
+This configuration option is obsolete since RTEMS 4.12.
+
+CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
+----------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
+
+This configuration option is obsolete since RTEMS 4.12.
+
+CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
+---------------------------------
+.. index:: CONFIGURE_MAXIMUM_POSIX_SPINLOCKS
+
+This configuration option is obsolete since RTEMS 4.12.
+
+CONFIGURE_SMP_APPLICATION
+-------------------------
+.. index:: CONFIGURE_SMP_APPLICATION
+
+This configuration option was introduced in RTEMS 4.11 and is obsolete since
+RTEMS 4.12.
+
+CONFIGURE_SMP_MAXIMUM_PROCESSORS
+--------------------------------
+.. index:: CONFIGURE_SMP_MAXIMUM_PROCESSORS
+
+This configuration option was introduced in RTEMS 4.11 and is obsolete since
+RTEMS 4.12. See also :ref:`CONFIGURE_MAXIMUM_PROCESSORS`.
More information about the vc
mailing list