rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-17 09:31:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

Shorten the name of the BSP and Device Driver Development Guide

Browse Source 
Old name:

    RTEMS BSP and Device Driver Development Guide

This is long and causes problems in the PDF output. This patch
changes the name to:

    RTEMS BSP and Driver Guide

Closes #3141.
This commit is contained in:
Joel Sherrill 2017-10-12 18:50:59 -05:00
parent 64564df810
commit c6f8e512b9
5 changed files with 11 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bsp-howto/conf.py
View File

@ -8,7 +8,7 @@ project = "RTEMS BSP and Device Driver Development Guide"
latex_documents = [
('index',
'bsp-howto.tex',
u'RTEMS BSP and Device Driver Development Guide',
u'RTEMS BSP and Driver Guide',
u'RTEMS Documentation Project',
'manual'),
]

6
bsp-howto/index.rst
View File

@ -1,8 +1,8 @@
.. comment SPDX-License-Identifier: CC-BY-SA-4.0
==========================================================
RTEMS BSP and Device Driver Development Guide (|version|).
==========================================================
=======================================
RTEMS BSP and Driver Guide (|version|).
=======================================
| **COPYRIGHT (c) 1988 - 2015.**
| **On-Line Applications Research Corporation (OAR).**

8
cpu-supplement/lattice_micro32.rst
View File

@ -186,13 +186,7 @@ Thread-local storage is not implemented.
Board Support Packages
======================
An RTEMS Board Support Package (BSP) must be designed to support a particular
processor model and target board combination.
In each of the architecture specific chapters, this section will present a
discussion of architecture specific BSP issues. For more information on
developing a BSP, refer to BSP and Device Driver Development Guide and the
chapter titled Board Support Packages in the RTEMS Applications User's Guide.
There are no Lattice Micro32 specific notes on BSPs.
System Reset
------------

8
cpu-supplement/port.rst
View File

@ -408,8 +408,8 @@ processor model and target board combination.
In each of the architecture specific chapters, this section will present a
discussion of architecture specific BSP issues. For more information on
developing a BSP, refer to BSP and Device Driver Development Guide and the
chapter titled Board Support Packages in the RTEMS Applications User's Guide.
developing a BSP, refer to *RTEMS BSP and Driver Guide* chapter titled
``Board Support Packages`` in the *RTEMS Classic API Guide*.
System Reset
------------
@ -418,5 +418,5 @@ An RTEMS based application is initiated or re-initiated when the processor is
reset or transfer is passed to it from a boot monitor or ROM monitor.
In each of the architecture specific chapters, this subsection describes the
actions that the BSP must tak assuming the application gets control when the
microprocessor is reset.
actions that the BSP must take assuming the application gets control
when the microprocessor is reset.

4
develenv/directory.rst
View File

@ -91,7 +91,7 @@ the RTEMS source tree. The top of the tree will be referenced as
subdirectory. Each ".cfg" file in this directory is associated with a
specific BSP and describes the CPU model, compiler flags, and procedure to
produce an executable for the target board. These files are described in
detail in the*RTEMS BSP and Device Driver Development Guide* and will not
detail in the *RTEMS BSP and Driver Guide* and will not
be discussed further in this document.
``${RTEMS_ROOT}/testsuites/``
@ -159,7 +159,7 @@ the subdirectories in this directory and a description of each.
specific source code for RTEMS. The ``libbsp/`` is organized based upon
the CPU family and boards BSPs. The contents of ``libbsp/`` are discussed
briefly in `c/src/lib/libbsp BSP Directory`_ and presented in detail in
the*RTEMS BSP and Device Driver Development Guide*. The ``libcpu/``
the *RTEMS BSP and Driver Guide*. The ``libcpu/``
directory is also organized by CPU family with further divisions based upon
CPU model and features that are shared across CPU models such as caching
and DMA.