Changeset d10e3b1 in rtems-docs


Ignore:
Timestamp:
Feb 17, 2020, 8:47:00 AM (6 months ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
5, master
Children:
ca1a9e6
Parents:
3738a74
git-author:
Sebastian Huber <sebastian.huber@…> (02/17/20 08:47:00)
git-committer:
Sebastian Huber <sebastian.huber@…> (02/24/20 13:58:25)
Message:

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:

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.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • c-user/configuring_a_system.rst

    r3738a74 rd10e3b1  
    19261926    ``CONFIGURE_EXTRA_TASK_STACKS``.
    19271927
    1928 .. index:: CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
    1929 
    1930 .. _CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE:
    1931 
    1932 CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
    1933 -----------------------------------------
    1934 
    1935 CONSTANT:
    1936     ``CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE``
    1937 
    1938 DATA TYPE:
    1939     Boolean feature macro.
    1940 
    1941 RANGE:
    1942     Defined or undefined.
    1943 
    1944 DEFAULT VALUE:
    1945     This is not defined by default.
    1946 
    1947 DESCRIPTION:
    1948     ``CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE`` is defined if the user wishes
    1949     to define their own POSIX API Initialization Threads Table.  This table
    1950     should be named ``POSIX_Initialization_threads``.
    1951 
    1952 NOTES:
    1953     This is a seldom used configuration parameter. The most likely use case is
    1954     when an application desires to have more than one initialization task.
    1955 
    19561928Configuring Custom Task Stack Allocation
    19571929========================================
     
    49674939This configuration option is obsolete since RTEMS 5.1.
    49684940
     4941.. index:: CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
     4942
     4943.. _CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE:
     4944
     4945CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE
     4946-----------------------------------------
     4947
     4948This configuration option was present in all RTEMS versions since at least 1995
     4949and is obsolete since RTEMS 5.1.  If you used this configuration option or you
     4950think that there should be a way to configure more than one POSIX initialization
     4951thread, then please ask on the  :r:list:`users`.
     4952
     4953.. index:: CONFIGURE_SMP_APPLICATION
     4954
     4955CONFIGURE_SMP_APPLICATION
     4956-------------------------
     4957
     4958This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
     4959RTEMS 5.1.
     4960
     4961.. index:: CONFIGURE_SMP_MAXIMUM_PROCESSORS
     4962
     4963CONFIGURE_SMP_MAXIMUM_PROCESSORS
     4964--------------------------------
     4965
     4966This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
     4967RTEMS 5.1.  See also :ref:`CONFIGURE_MAXIMUM_PROCESSORS`.
     4968
    49694969.. index:: CONFIGURE_TERMIOS_DISABLED
    49704970
     
    49734973
    49744974This configuration option is obsolete since RTEMS 5.1.
    4975 
    4976 .. index:: CONFIGURE_SMP_APPLICATION
    4977 
    4978 CONFIGURE_SMP_APPLICATION
    4979 -------------------------
    4980 
    4981 This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
    4982 RTEMS 5.1.
    4983 
    4984 .. index:: CONFIGURE_SMP_MAXIMUM_PROCESSORS
    4985 
    4986 CONFIGURE_SMP_MAXIMUM_PROCESSORS
    4987 --------------------------------
    4988 
    4989 This configuration option was introduced in RTEMS 4.11.0 and is obsolete since
    4990 RTEMS 5.1.  See also :ref:`CONFIGURE_MAXIMUM_PROCESSORS`.
Note: See TracChangeset for help on using the changeset viewer.