Changeset 6682434 in rtems-docs


Ignore:
Timestamp:
Dec 20, 2018, 3:17:09 PM (10 months ago)
Author:
Joel Sherrill <joel@…>
Branches:
master
Children:
e4087f0
Parents:
e24c5e9
Message:

Eliminate UTF-8 characters except superscripted 2 in i2c

Files:
9 edited

Legend:

Unmodified
Added
Removed
  • eng/appendix-a.rst

    re24c5e9 r6682434  
    1010An effort at NASA has been performed to suggest a core set of artifacts
    1111(as defined by **BOTH** NASA NPR 7150.2B and DO-178B) that can be utilized
    12 by a mission as a baselined starting point for “pre-qualification”
     12by a mission as a baselined starting point for "pre-qualification"
    1313for (open-source) software that is intended to be utilized for flight
    1414purposes.  This effort analyzed the overlap between NPR 7150.2B
     
    127127   |                |                       | verification activities.        |
    128128   +----------------+-----------------------+---------------------------------+
    129    | Usability      | Software User’s       | The Software User Manual        |
     129   | Usability      | Software User's       | The Software User Manual        |
    130130   |                | Manual                | defines user instructions for   |
    131131   |                |                       | the software.                   |
     
    134134In an effort to remain lightweight and sustainable for open-source
    135135projects, Table 1 above was condensed into a single artifact outline
    136 that encompasses the artifacts’ intents.  The idea is that this living
     136that encompasses the artifacts' intents.  The idea is that this living
    137137qualification document will reside under RTEMS source control and be
    138138updated with additional detail accordingly.  The artifact outline is
  • eng/license-requirements.rst

    re24c5e9 r6682434  
    1010All artifacts shall adhere to RTEMS Project licensing
    1111requirements. Currently, the preferred licenses are CC-BY-SA-4.0 license
    12 for documentation and “Two Paragraph BSD” for source code.
     12for documentation and "Two Paragraph BSD" for source code.
    1313
    1414Historically, RTEMS has been licensed under the GPL v2 with linking
  • eng/prequalification.rst

    re24c5e9 r6682434  
    1515standards typically do not specify software functionality but address
    1616topics like requirements definition, traceability, having a documented
    17 change process, coding style, testing requirements, and a user’s
    18 manual. During system test, these standards call for a review – usually
    19 by an independent entity – that the standard has been adhered too. These
     17change process, coding style, testing requirements, and a user's
     18manual. During system test, these standards call for a review - usually
     19by an independent entity - that the standard has been adhered too. These
    2020reviews cover a broad variety of topics and activities, but the process
    2121is generally referred to as qualification, verification, or auditing
    2222against the specific standard in use. The RTEMS Project will use the
    23 term “qualification” independent of the standard.
     23term "qualification" independent of the standard.
    2424
    2525The goal of the RTEMS Qualification Project is to make RTEMS easier
     
    3737
    3838The RTEMS Qualification Project is technically
    39 â€œpre-qualification”. True qualification must be performed on the
    40 project’s target hardware in a system context. The FAA has provided
     39"pre-qualification." True qualification must be performed on the
     40project's target hardware in a system context. The FAA has provided
    4141guidance for Reusable Software Components (FAA-AC20-148) and this
    4242effort should follow that guidance. The open RTEMS Project, with the
     
    5454on qualification should be able to provide resources for improving the
    5555automated project infrastructure and master technical data for RTEMS. The
    56 term “resources” is often used by open source projects to refer to
     56term "resources" is often used by open source projects to refer to
    5757volunteer code contributions or funding. Although code contributions in
    5858this area are important and always welcome, funding is also important. At
     
    7575It is expected that the RTEMS Qualification Project will create and
    7676maintain maps from the RTEMS master technical data to the various
    77 qualification standards. It will maintain “scorecards” which
     77qualification standards. It will maintain "scorecards" which
    7878identify how the RTEMS Project is currently doing when reviewed per each
    7979standard. These will be maintained in the open as community resources
  • eng/test-plan.rst

    re24c5e9 r6682434  
    2222Assuming that a requirements focused test suite is added to the open
    2323RTEMS, tools will be needed to assist in verifying that requirements are
    24 â€œfully tested.” A fully tested requirement is one which is implemented
     24"fully tested." A fully tested requirement is one which is implemented
    2525and tested with associated logical tracing. Tools automating this analysis
    2626and generating reporting and alerts will be a critical part of ensuring
  • eng/users-manuals.rst

    re24c5e9 r6682434  
    1010TBD - write and link to useful documentation, potential URLs:
    1111
    12 Reference the RTEMS C User’s Manual
     12Reference the RTEMS Classic API Guide
    1313
    1414* https://docs.rtems.org/doc-current/share/rtems/pdf/c_user.pdf
  • eng/vc-authors.rst

    re24c5e9 r6682434  
    2626Currently all committer's should have an ssh account on the main git server,
    2727dispatch.rtems.org. If you have been granted commit access and do have an
    28 account on dispatch.rtems.org one should be requested on the devel@
 list.
     28account on dispatch.rtems.org one should be requested on the devel@ list.
    2929SSH access for git uses key logins instead of passwords. The key should be at
    30 least 1024bits in length.
     30least 1024 bits in length.
    3131
    3232The public repositories can by cloned with
     
    4343user with a personal repository can make commits, create and delete branches,
    4444plus more without interfering with the master repository. Commits to the
    45 master repository generate email to the vc@
 list and development type commits
     45master repository generate email to the vc@ list and development type commits
    4646by a developer would only add noise and lessen the effectiveness of the commit
    4747list
  • eng/vc-users.rst

    re24c5e9 r6682434  
    385385An alternative to the merge command is rebase, which replays the changes
    386386(commits) on one branch onto another. ``git rebase`` finds the common ancestor
    387 of the two branches, stores each commit of the branch you’re on to temporary
     387of the two branches, stores each commit of the branch you are on to temporary
    388388files and applies each commit in order.
    389389
  • user/tracing/examples.rst

    re24c5e9 r6682434  
    5757the full path instead of the path file: `sparc-rtems5/erc32/lib/` in the
    5858following commands according to your installation. Also confirm the path of the
    59 fileio’s executable and object files in the last line of the command according
     59fileio's executable and object files in the last line of the command according
    6060to your installation.
    6161
  • user/tracing/introduction.rst

    re24c5e9 r6682434  
    4141used to build the application for performing this link.
    4242
    43 Step 2: The RTEMS Trace Linker reads the user’s configuration file and that
     43Step 2: The RTEMS Trace Linker reads the user's configuration file and that
    4444results in it reading the standard Trace Buffering Configuration files
    4545installed with the RTEMS Trace Linker. The trace linker uses the target
    4646compiler and linker to create the trace enabled application executable. It
    47 wraps the functions defined in the user’s configuration with code that captures
     47wraps the functions defined in the user's configuration with code that captures
    4848trace records into the statically allocated buffer. The trace wrapper code is
    4949compiled with the target compiler and the resulting ELF object file is added to
     
    5454the target hardware or simulator.
    5555
    56 Step 4: RTEMS shell provides the “rtrace” command to display and save trace
     56Step 4: RTEMS shell provides the "rtrace" command to display and save trace
    5757buffers.
    5858
Note: See TracChangeset for help on using the changeset viewer.