From 92ea6e0b944e3830e05570ba99ff0e39fd158f1b Mon Sep 17 00:00:00 2001
From: Franc Urbanc <franc.urbanc@arm.com>
Date: Wed, 5 Jun 2024 11:53:45 +0200
Subject: [PATCH] Documentation: remove CMSIS-RTOS v1 compatibility layer

---
 .../Doxygen/Network/src/network_resource_requirements.txt    | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/Documentation/Doxygen/Network/src/network_resource_requirements.txt b/Documentation/Doxygen/Network/src/network_resource_requirements.txt
index fb74d266..a71b6b0e 100644
--- a/Documentation/Doxygen/Network/src/network_resource_requirements.txt
+++ b/Documentation/Doxygen/Network/src/network_resource_requirements.txt
@@ -36,13 +36,10 @@ file located under the \b Device component class.
 
 \section nw_rtos_req CMSIS-RTOS Requirements
 
-Currently, the Network component works in three different RTOS configurations:
+Currently, the Network component works in two different RTOS configurations:
 -# <b>CMSIS-RTOS2 RTX5</b>: This mode uses Keil RTX5 natively. In the Manage Run-Time Environment window, the component
    <b>CMSIS:RTOS2 (API):Keil RTX5</b> must be selected. The RTOS resources are static, configured by the system. There is
    <b>no need for additional user configuration</b>. This is the suggested option for new development.
--# <b>CMSIS-RTOS RTX5</b>: this mode uses RTX5 under a compatibility layer, which uses CMSIS-RTOS v1.
-   In the Manage Run-Time Environment window, the components <b>CMSIS:RTOS (API):Keil RTX5</b> and
-   <b>CMSIS:RTOS2 (API):Keil RTX5</b> must be selected.
 -# <b>CMSIS-RTOS2 with a generic RTOS</b>: this mode uses a generic RTOS (such as FreeRTOS). The RTOS
    resources (thread, mutex and semaphore control blocks and thread stacks) are dynamically allocated. The user needs to
    provide memory pools big enough for the allocations in RTOS configuration.