diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-02-17 09:47:00 +0100 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-02-24 14:58:25 +0100 |
commit | d10e3b1a7e4ffcede23c5e6ca6c79a0a2cafaaa1 (patch) | |
tree | 7370c209157815d63deb112b3f0829ee84f7e2f1 /c-user/configuring_a_system.rst | |
parent | c-user: Obsolete CONFIGURE_HAS_OWN_INIT_TASK_TABLE (diff) | |
download | rtems-docs-d10e3b1a7e4ffcede23c5e6ca6c79a0a2cafaaa1.tar.bz2 |
c-user: Obsolete CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_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_POSIX_HAS_OWN_INIT_THREAD_TABLE would have required the
use of the undocumented CONFIGURE_POSIX_INIT_THREAD_TABLE_NAME and
CONFIGURE_POSIX_INIT_THREAD_TABLE_SIZE configuration options.
Close #3874.
Diffstat (limited to '')
-rw-r--r-- | c-user/configuring_a_system.rst | 48 |
1 files changed, 16 insertions, 32 deletions
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst index 44f3ef8..230d6b6 100644 --- a/c-user/configuring_a_system.rst +++ b/c-user/configuring_a_system.rst @@ -1925,34 +1925,6 @@ NOTES: Task/Thread Stack Memory Above Minimum` for more information about ``CONFIGURE_EXTRA_TASK_STACKS``. -.. index:: CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE - -.. _CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE: - -CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE ------------------------------------------ - -CONSTANT: - ``CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE`` - -DATA TYPE: - Boolean feature macro. - -RANGE: - Defined or undefined. - -DEFAULT VALUE: - This is not defined by default. - -DESCRIPTION: - ``CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE`` is defined if the user wishes - to define their own POSIX API Initialization Threads Table. This table - should be named ``POSIX_Initialization_threads``. - -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. - Configuring Custom Task Stack Allocation ======================================== @@ -4966,12 +4938,17 @@ CONFIGURE_MAXIMUM_POSIX_SPINLOCKS This configuration option is obsolete since RTEMS 5.1. -.. index:: CONFIGURE_TERMIOS_DISABLED +.. index:: CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE -CONFIGURE_TERMIOS_DISABLED --------------------------- +.. _CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE: -This configuration option is obsolete since RTEMS 5.1. +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 @@ -4988,3 +4965,10 @@ 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. |