summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2020-02-17 09:41:40 +0100
committerSebastian Huber <sebastian.huber@embedded-brains.de>2020-02-24 14:58:25 +0100
commit3738a74014753ca37891f0725ca72ca82dd4391e (patch)
treefc0c4084b736b0fb30a6f196d205d17214fffefc
parent03facdaef8ab163b1ce4d7cad6df79ceccf98344 (diff)
downloadrtems-docs-3738a74014753ca37891f0725ca72ca82dd4391e.tar.bz2
c-user: Obsolete CONFIGURE_HAS_OWN_INIT_TASK_TABLE
The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_* configuration options. These two options are probably unused, see also: * https://lists.rtems.org/pipermail/users/2019-April/033129.html * https://lists.rtems.org/pipermail/users/2019-April/033130.html Removing them simplifies the configuration. If there is a real user need which shows up after the removal, we can resurrect them on demand. Using CONFIGURE_HAS_OWN_INIT_TASK_TABLE would have required the use of the undocumented CONFIGURE_INIT_TASK_TABLE and CONFIGURE_INIT_TASK_TABLE_SIZE configuration options. Close #3873.
-rw-r--r--c-user/configuring_a_system.rst40
1 files changed, 12 insertions, 28 deletions
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
index b23527a..44f3ef8 100644
--- a/c-user/configuring_a_system.rst
+++ b/c-user/configuring_a_system.rst
@@ -1575,34 +1575,6 @@ DESCRIPTION:
NOTES:
None.
-.. index:: CONFIGURE_HAS_OWN_INIT_TASK_TABLE
-
-.. _CONFIGURE_HAS_OWN_INIT_TASK_TABLE:
-
-CONFIGURE_HAS_OWN_INIT_TASK_TABLE
----------------------------------
-
-CONSTANT:
- ``CONFIGURE_HAS_OWN_INIT_TASK_TABLE``
-
-DATA TYPE:
- Boolean feature macro.
-
-RANGE:
- Defined or undefined.
-
-DEFAULT VALUE:
- This is not defined by default.
-
-DESCRIPTION:
- ``CONFIGURE_HAS_OWN_INIT_TASK_TABLE`` is defined if the user wishes to
- define their own Classic API Initialization Tasks Table. This table should
- be named ``Initialization_tasks``.
-
-NOTES:
- This is a seldom used configuration parameter. The most likely use case is
- when an application desires to have more than one initialization task.
-
POSIX API Configuration
=======================
@@ -4873,6 +4845,18 @@ 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