summaryrefslogtreecommitdiffstats
path: root/posix-compliance/standards.rst
diff options
context:
space:
mode:
authorJoel Sherrill <joel@rtems.org>2021-04-06 16:56:01 -0500
committerJoel Sherrill <joel@rtems.org>2021-04-07 13:57:57 -0500
commitb43fe709af0130dd720b61aa505da2c23d9c3c81 (patch)
tree4c81848a51f19f3eeb14718601647059dbf003d2 /posix-compliance/standards.rst
parent241cd068d3e1539b37181a78cd0f6ce12b5e5309 (diff)
downloadrtems-docs-b43fe709af0130dd720b61aa505da2c23d9c3c81.tar.bz2
posix-compliance: Update tracking spreadsheet to v12
The new version of the API tracking spreadsheet includes FACE Technical Standard, Edition 3.1 as well as a few additions to what RTEMS supports. The generation script and discussion of standards was updated to reflect the inclusion of a new Edition of the FACE Technical Standard. Closes #4380.
Diffstat (limited to 'posix-compliance/standards.rst')
-rw-r--r--posix-compliance/standards.rst20
1 files changed, 13 insertions, 7 deletions
diff --git a/posix-compliance/standards.rst b/posix-compliance/standards.rst
index ea86b94..4e6ed3b 100644
--- a/posix-compliance/standards.rst
+++ b/posix-compliance/standards.rst
@@ -69,21 +69,27 @@ and 2.1.1. In these editions, the profiles are as follows:
* General Purpose - 812 APIs, multi-process, much more
-FACE Technical Standard Edition 3.0 adds the requirement for an
+FACE Technical Standard, Edition 3.0 adds the requirement for an
operating system to support ``clock_nanosleep()`` in all profiles and
defines one additional subcommand for the ``posix_devctl()`` methods.
+FACE Technical Standard, Edition 3.1 has a number of minor changes
+to the profiles. Most of these were to improve alignment with the
+Software Communications Architecture (SCA) profiles. Additionally,
+some inconsistencies in the profiles were noticed and addressed while
+doing the alignment review.
+
RTEMS provides all of the methods required by the FACE Safety BASE profile
and all of the methods in the Safety Extended profile which do not require
multiple processes. Similarly, RTEMS provides most of the methods in the
General Purpose profile which do not require multiple processes.
-The Software Communications Architecture (SCA) specification targets the
-requirements for software-defined radios. This specification was originally
-developed in support of the Joint Tactical Radio System (JTRS) program
-in conjunction with the Object Management Group (OMG). This standard is
-now maintained by the Wireless Innovation Forum with support from the
-U.S. Navy Joint Tactical Network Center (JTNC). Some URLs of interest:
+The SCA specification targets the requirements for software-defined
+radios. This specification was originally developed in support of the
+Joint Tactical Radio System (JTRS) program in conjunction with the Object
+Management Group (OMG). This standard is now maintained by the Wireless
+Innovation Forum with support from the U.S. Navy Joint Tactical Network
+Center (JTNC). Some URLs of interest:
* SCA at Wireless Innovation Forum - http://www.wirelessinnovation.org/sca-based-standards-library