rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-17 22:41:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

c-user: Obsolete CONFIGURE_HAS_OWN_INIT_TASK_TABLE

Browse Source 
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.
This commit is contained in:
Sebastian Huber 2020-02-17 09:41:40 +01:00
parent 03facdaef8
commit 3738a74014
1 changed files with 12 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
c-user/configuring_a_system.rst
View File

@ -1575,34 +1575,6 @@ DESCRIPTION:
NOTES: NOTES:
None. 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 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 This configuration option was present in all RTEMS versions since at least 1995
and is obsolete since RTEMS 5.1. 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 .. index:: CONFIGURE_HAS_OWN_MOUNT_TABLE
CONFIGURE_HAS_OWN_MOUNT_TABLE CONFIGURE_HAS_OWN_MOUNT_TABLE