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.
This commit is contained in:
Joel Sherrill 2021-04-06 16:56:01 -05:00
parent 241cd068d3
commit b43fe709af
5 changed files with 1398 additions and 1364 deletions

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -28,6 +28,10 @@ standards = [
'FACE 3.0 Safety Base', 'FACE 3.0 Safety Base',
'FACE 3.0 Safety Extended', 'FACE 3.0 Safety Extended',
'FACE 3.0 General Purpose', 'FACE 3.0 General Purpose',
'FACE 3.1 Security',
'FACE 3.1 Safety Base',
'FACE 3.1 Safety Extended',
'FACE 3.1 General Purpose',
'SCA 2.2.2 AEP', 'SCA 2.2.2 AEP',
'SCA 4.1 Ultra Lightweight AEP', 'SCA 4.1 Ultra Lightweight AEP',
'SCA 4.1 Lightweight AEP', 'SCA 4.1 Lightweight AEP',
@ -52,6 +56,10 @@ standard_names = {
'FACE 3.0 Safety Base' : 'FACE 3.0 Safety Base', 'FACE 3.0 Safety Base' : 'FACE 3.0 Safety Base',
'FACE 3.0 Safety Extended': 'FACE 3.0 Safety Extended', 'FACE 3.0 Safety Extended': 'FACE 3.0 Safety Extended',
'FACE 3.0 General Purpose': 'FACE 3.0 General Purpose', 'FACE 3.0 General Purpose': 'FACE 3.0 General Purpose',
'FACE 3.1 Security' : 'FACE 3.1 Security',
'FACE 3.1 Safety Base' : 'FACE 3.1 Safety Base',
'FACE 3.1 Safety Extended': 'FACE 3.1 Safety Extended',
'FACE 3.1 General Purpose': 'FACE 3.1 General Purpose',
'SCA 2.2.2 AEP' : 'SCA 2.2.2 AEP', 'SCA 2.2.2 AEP' : 'SCA 2.2.2 AEP',
'SCA 4.1 Ultra Lightweight AEP' : 'SCA 4.1 Ultra Lightweight AEP', 'SCA 4.1 Ultra Lightweight AEP' : 'SCA 4.1 Ultra Lightweight AEP',
'SCA 4.1 Lightweight AEP' : 'SCA 4.1 Lightweight AEP', 'SCA 4.1 Lightweight AEP' : 'SCA 4.1 Lightweight AEP',
@ -79,6 +87,10 @@ col_names = {
'FACE 3.0 Safety Base' : 'FACE 3.0 Safety Base', 'FACE 3.0 Safety Base' : 'FACE 3.0 Safety Base',
'FACE 3.0 Safety Extended' : 'FACE 3.0 Safety Extended', 'FACE 3.0 Safety Extended' : 'FACE 3.0 Safety Extended',
'FACE 3.0 General Purpose' : 'FACE 3.0 General Purpose', 'FACE 3.0 General Purpose' : 'FACE 3.0 General Purpose',
'FACE 3.1 Security' : 'FACE 3.1 Security',
'FACE 3.1 Safety Base' : 'FACE 3.1 Safety Base',
'FACE 3.1 Safety Extended' : 'FACE 3.1 Safety Extended',
'FACE 3.1 General Purpose' : 'FACE 3.1 General Purpose',
'SCA 2.2.2 AEP' : 'SCA 2.2.2 AEP', 'SCA 2.2.2 AEP' : 'SCA 2.2.2 AEP',
'SCA 4.1 Ultra Lightweight AEP' : 'SCA 4.1 Ultra Lightweight AEP', 'SCA 4.1 Ultra Lightweight AEP' : 'SCA 4.1 Ultra Lightweight AEP',
'SCA 4.1 Lightweight AEP' : 'SCA 4.1 Lightweight AEP', 'SCA 4.1 Lightweight AEP' : 'SCA 4.1 Lightweight AEP',

View File

@ -69,21 +69,27 @@ and 2.1.1. In these editions, the profiles are as follows:
* General Purpose - 812 APIs, multi-process, much more * 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 operating system to support ``clock_nanosleep()`` in all profiles and
defines one additional subcommand for the ``posix_devctl()`` methods. 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 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 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 multiple processes. Similarly, RTEMS provides most of the methods in the
General Purpose profile which do not require multiple processes. General Purpose profile which do not require multiple processes.
The Software Communications Architecture (SCA) specification targets the The SCA specification targets the requirements for software-defined
requirements for software-defined radios. This specification was originally radios. This specification was originally developed in support of the
developed in support of the Joint Tactical Radio System (JTRS) program Joint Tactical Radio System (JTRS) program in conjunction with the Object
in conjunction with the Object Management Group (OMG). This standard is Management Group (OMG). This standard is now maintained by the Wireless
now maintained by the Wireless Innovation Forum with support from the Innovation Forum with support from the U.S. Navy Joint Tactical Network
U.S. Navy Joint Tactical Network Center (JTNC). Some URLs of interest: Center (JTNC). Some URLs of interest:
* SCA at Wireless Innovation Forum - http://www.wirelessinnovation.org/sca-based-standards-library * SCA at Wireless Innovation Forum - http://www.wirelessinnovation.org/sca-based-standards-library

View File

@ -24,7 +24,7 @@ def gen_posix_rst(task):
def build(ctx): def build(ctx):
ctx(rule = gen_posix_rst, ctx(rule = gen_posix_rst,
source = ['posix_rst.py', 'RTEMS-Standards-Compliance-v9.csv'], source = ['posix_rst.py', 'RTEMS-Standards-Compliance-v12.csv'],
target = 'generated-posix-compliance.rst') target = 'generated-posix-compliance.rst')
sources = { 'extra' : ['generated-posix-compliance.rst'] } sources = { 'extra' : ['generated-posix-compliance.rst'] }
doc_build(ctx, sources = sources) doc_build(ctx, sources = sources)