diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2019-01-23 10:40:40 +0100 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2019-01-24 07:31:25 +0100 |
| commit | 63735bc9d2ec845ebe070c9eb0bb45f60aefdebc (patch) | |
| tree | 7d522088c8fe1c090bcc975536dc151a4a89e7c5 /user/hardware | |
| parent | user: Stub documentation for griscv BSP (diff) | |
| download | rtems-docs-63735bc9d2ec845ebe070c9eb0bb45f60aefdebc.tar.bz2 | |
user: Spell out third-party
Diffstat (limited to 'user/hardware')
| -rw-r--r-- | user/hardware/targets.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/user/hardware/targets.rst b/user/hardware/targets.rst index 4d5e87f..0357be7 100644 --- a/user/hardware/targets.rst +++ b/user/hardware/targets.rst @@ -12,7 +12,7 @@ Targets *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 +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 |