The content introduced by a commit in the RTEMS main repository
commit 418de420a05609ba8919822b553706963a8d3a7b
Author: Joel Sherrill <joel.sherrill@OARcorp.com>
Date: Wed Oct 5 19:59:47 2011 +0000
2011-10-05 Joel Sherrill <joel.sherrill@oarcorp.com>
Petr Benes <benesp16@fel.cvut.cz>
PR 1912/doc
* user/conf.t, user/schedule.t: Rework to add scheduler specific
information.
is no longer in this file. According to the file history, this was the
only content introduced by Petr Benes. Also during the relicensing of
the documentation to CC-BY-SA-4.0 in 2016 it was proclaimed that OAR was
the only copyright holder of the RTEMS documentation present in the
RTEMS main repository.
Update #3836.
Add a description of the previously missing RTEMS_NOT_DEFINED return
value for rtems_rate_monotonic_get_status().
Update the RTEMS_SUCCESSFUL return value descriptions for
rtems_rate_monotonic_get_status() and
rtems_rate_monotonic_get_statistics() which incorrectly used the same
description as rtems_rate_monotonic_period().
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.
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.
Define exactly one term per definition. Use references for alternative
terms. Add :term: text roles to acronym definitions of glossary defined
terms.
Update #3853.
Move CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS to general system
configuration. Remove now empty "C Library Support Configuration"
section.
Update #3836.
Remove the unfinished sentence
"Since a barrier is, by definition, never immediately [...]"
and jump directly to
"The task may wait [forever or for a timeout]"
instead.
I cannot figure out what the unfinished sentence is supposed to be -
"released"? "passed"?
Remove various incorrect references to "lock" and "obtain" and to an
option set which is not part of the barrier interface.
It looks like the barrier documentation was started based on a copy of
the semaphore documentation and these things are surviving remnants.
Also remove an unfinished sentence in the barrier wait description,
since the intended information is already provided in the under the NOTE
label.
