michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: posix: overview: add missing :ref: in subprofiles section

Browse source 
Previously, some links were not resolving properly since they
lacked the :ref: prefix, so it was added.

Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
This commit is contained in:
Chris Friedt 2024-04-21 12:25:21 -04:00 • committed by Carles Cufí
commit ee2c2f6488
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/services/portability/posix/overview/index.rst
View file

@ -38,11 +38,12 @@ Benefits of POSIX support in Zephyr include:
POSIX Subprofiles POSIX Subprofiles
================= =================
While Zephyr supports running multiple `threads <threads_v2>` (possibly in an `SMP <smp_arch>` While Zephyr supports running multiple :ref:`thread <threads_v2>` (possibly in an
configuration), as well as `Virtual Memory and MMUs <memory_management_api>`, Zephyr code and data :ref:`SMP <smp_arch>` configuration), as well as
normally share a common address space. The Zephyr kernel executable code and the application :ref:`Virtual Memory and MMUs <memory_management_api>`, Zephyr code and data normally share a
executable code are typically compiled into the same binary artifact. From that perspective, Zephyr common address space. The Zephyr kernel executable code and the application executable code are
apps can be seen as running in the context of a single process. typically compiled into the same binary artifact. From that perspective, Zephyr apps can be seen
as running in the context of a single process.
While multi-purpose operating systems (OS) offer full POSIX conformance, Real-Time Operating While multi-purpose operating systems (OS) offer full POSIX conformance, Real-Time Operating
Systems (RTOS) such as Zephyr typically serve a fixed-purpose, have limited hardware resources, Systems (RTOS) such as Zephyr typically serve a fixed-purpose, have limited hardware resources,