[incubator-nuttx] 03/05: Documentation/esp32: The linker scripts now is generated to decided wether to run from IRAM or Flash based on Kconfig options.

[sa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sara pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git

commit 96d093a5454ca67dfc8a6ed1f37004aa215f1115
Author: Abdelatif Guettouche <ab...@espressif.com>
AuthorDate: Mon Jul 26 21:23:40 2021 +0200

    Documentation/esp32: The linker scripts now is generated to decided
    wether to run from IRAM or Flash based on Kconfig options.
    
    Signed-off-by: Abdelatif Guettouche <ab...@espressif.com>
---
 Documentation/platforms/xtensa/esp32/index.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Documentation/platforms/xtensa/esp32/index.rst b/Documentation/platforms/xtensa/esp32/index.rst
index 3ce15c3..a3ed9f4 100644
--- a/Documentation/platforms/xtensa/esp32/index.rst
+++ b/Documentation/platforms/xtensa/esp32/index.rst
@@ -587,8 +587,7 @@ Running from IRAM is a good debug option.  You should be able to load the
 ELF directly via JTAG in this case, and you may not need the bootloader.
 
 NuttX supports a configuration option, CONFIG_ESP32_DEVKITC_RUN_IRAM, that may be
-selected for execution from IRAM.  This option simply selects the correct
-linker script for IRAM execution.
+selected for execution from IRAM.
 
 Skipping the Secondary Bootloader
 ---------------------------------