summaryrefslogtreecommitdiffstats
path: root/user/hardware/targets.rst
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2019-01-11 14:44:36 +0100
committerSebastian Huber <sebastian.huber@embedded-brains.de>2019-01-14 07:15:27 +0100
commit3de74baacbb4145642d0e058846485bb4a3f631f (patch)
tree0ca1c20a49f765a293dd06b2ec69e6cc17a623e3 /user/hardware/targets.rst
parent89a33b3db80521673bdd7c180f95b834e7f303d4 (diff)
downloadrtems-docs-3de74baacbb4145642d0e058846485bb4a3f631f.tar.bz2
user: Rework "Hardware" chapter
Rename it to "Target Hardware". Remove BSPs section and reference the BSPs chapter instead. Remove explicit list of architectures and reference the BSPs chapter instead. Fix typos. Elaborate multilib description in the architecture section.
Diffstat (limited to 'user/hardware/targets.rst')
-rw-r--r--user/hardware/targets.rst28
1 files changed, 14 insertions, 14 deletions
diff --git a/user/hardware/targets.rst b/user/hardware/targets.rst
index 943d77b..4d5e87f 100644
--- a/user/hardware/targets.rst
+++ b/user/hardware/targets.rst
@@ -8,19 +8,19 @@ Targets
=======
.. index:: Targets
-Hardware that can run RTEMS is often referred to as a *target* because RTEMS is
-specifically aimed at that hardware or target. An RTEMS executable is
-statically linked and executes in a single address space on the target
-hardware. A statically linked executable means the RTEMS Kernel, drivers, third
-party packages and application code is linked into a single executable image. A
-single address space means no virtual memory and no memory protected process
-address space is running within the RTEMS arena and the RTEMS Kernel, drivers
-and application have unprotected access to the whole address space and all
-hardware.
-
-Target hardware supported by RTEMS has a Board Support Package or BSP. A BSP is
-a specific instance of an RTEMS architecture that allows the creation of an
-RTEMS executable. You can view the layering as:
+*Target hardware* that can run RTEMS is often referred to simply as the
+*target* because RTEMS is specifically aimed at that target hardware. An RTEMS
+executable is statically linked and executes in a single address space on the
+target hardware. A statically linked executable means the RTEMS Kernel,
+drivers, third party packages and application code is linked into a single
+executable image. A single address space means no virtual memory and no memory
+protected process address space is running within the RTEMS arena and the RTEMS
+executive, drivers and application have unprotected access to the whole address
+space and all hardware.
+
+Target hardware supported by RTEMS has a :ref:`Board Support Package <BSPs>` or
+BSP. A BSP is a specific instance of an RTEMS architecture that allows the
+creation of an RTEMS executable. You can view the layering as:
.. comment Build image with:
.. comment aafigure hw-layers.txt --textual --type png --option
@@ -31,7 +31,7 @@ RTEMS executable. You can view the layering as:
:align: center
:alt: Software Layers on Hardware
-RTEMS Targets are grouped by architectures and within an architecture there are
+RTEMS targets are grouped by architectures and within an architecture there are
a number of Board Support Packages or BPSs. An architecture is a specific class
or family of processors and can be large such as ARM or specific such as the
NIOS-II or Microblaze.