From d55225eb29b8d3e68cdd5dc922c6d241afc21c85 Mon Sep 17 00:00:00 2001 From: Gunar Schorcht Date: Fri, 16 Aug 2019 16:01:49 +0200 Subject: [PATCH] cpu/esp32: remove SDK crypto dependency from doc --- cpu/esp32/doc.txt | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/cpu/esp32/doc.txt b/cpu/esp32/doc.txt index 75ee6cbd3b..0e69607ab3 100644 --- a/cpu/esp32/doc.txt +++ b/cpu/esp32/doc.txt @@ -192,7 +192,6 @@ The RIOT-OS for ESP32 SoCs supports the following features at the moment: The implementation of RIOT-OS for ESP32 SOCs has the following limitations at the moment: - Only one core (the PRO CPU) is used because RIOT does not support running multiple threads simultaneously. -- RIOT modules crypto and hashes cannot be used together with modules esp_now and esp_wifi - Bluetooth cannot be used at the moment. - Flash encryption is not yet supported. @@ -942,12 +941,9 @@ The board has to have one of the supported PHY modules to be able to use the Eth The RIOT port for ESP32 implements in module `esp_wifi` a `netdev` driver for the built-in WiFi interface. -@note Due to symbol conflicts with the `crypto` and `hash` modules of RIOT -in module `esp_idf_wpa_supplicant_crypto`, which is required by module -`esp_wifi`, `esp_wifi` cannot be used for applications that use these modules. -Therefore, module `esp_wifi` is not automatically enabled when module -`netdev_default` is used. Instead, if necessary, the application has to add -the module `esp_wifi` in the Makefile. +@note Module `esp_wifi` is not enabled automatically when the `netdev_default` +module is used. Instead, if necessary, the application has to add the +`esp_wifi` module in the Makefile. ``` USEMODULE += esp_wifi @@ -987,7 +983,9 @@ With ESP-NOW, the ESP32 provides a connectionless communication technology, feat The RIOT port for ESP32 implements in module ```esp_now``` a ```netdev``` driver which uses ESP-NOW to provide a link layer interface to a meshed network of ESP32 nodes. In this network, each node can send short packets with up to 250 data bytes to all other nodes that are visible in its range. -@note Due to symbol conflicts in the ```esp_idf_wpa_supplicant_crypto``` module used by the ```esp_now``` with RIOT's ```crypto``` and ```hashes``` modules, ESP-NOW cannot be used for application that use these modules. Therefore, the module ```esp_now``` is not enabled automatically if the ```netdev_default``` module is used. Instead, the application has to add the ```esp_now``` module in its makefile when needed.
+@note Module `esp_now`module is not enabled automatically if the +`netdev_default` module is used. Instead, the application has to add the +`esp_now` module in its makefile when needed.
``` USEMODULE += esp_now ```