doc: move cmsis rtos API docs to portability/

Move CMSIS RTOS API docs under portability to distinguish from
architecture and board porting.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2019-07-14 08:41:48 -04:00
commit 65eebd33d9
6 changed files with 19 additions and 16 deletions

View file

@ -7,6 +7,7 @@ User and Developer Guides
:maxdepth: 1
getting-help.rst
portability/index.rst
bluetooth/index.rst
c_library
../README.rst

View file

@ -0,0 +1,18 @@
.. _osal:
OS Abstraction
##############
OS abstraction layers (OSAL) provide wrapper function APIs that
encapsulate common system functions offered by any operating system.
These APIs make it easier and quicker to develop for, and port code to
multiple software and hardware platforms.
These sections describe the software and hardware abstraction layers
supported by the Zephyr RTOS.
.. toctree::
:maxdepth: 1
cmsis_rtos_v1.rst
cmsis_rtos_v2.rst

View file

@ -12,5 +12,4 @@ API interfaces supported by Zephyr.
arch.rst
board_porting.rst
porting_to_zephyr.rst
shields.rst

View file

@ -1,15 +0,0 @@
.. _porting_to_zephyr:
Porting Applications to Zephyr
##############################
This section describes standard API interfaces supported by Zephyr.
Applications written using standard API interfaces are supposed to
be OS agnostic. Supporting such APIs in Zephyr would make it easier
to port those applications to Zephyr.
.. toctree::
:maxdepth: 1
cmsis_rtos_v1.rst
cmsis_rtos_v2.rst