[rtems-docs commit] Remove BSP_ZERO_WORKSPACE_AUTOMATICALLY

Sebastian Huber sebh at rtems.org
Thu Feb 6 14:24:17 UTC 2020


Module:    rtems-docs
Branch:    master
Commit:    df2dcdbabc4849dd23d5dfb45e0e482f4cdafbd3
Changeset: http://git.rtems.org/rtems-docs/commit/?id=df2dcdbabc4849dd23d5dfb45e0e482f4cdafbd3

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Tue Feb  4 13:16:28 2020 +0100

Remove BSP_ZERO_WORKSPACE_AUTOMATICALLY

Close #3863.

---

 bsp-howto/miscellanous_support.rst |  7 -------
 c-user/configuring_a_system.rst    | 32 ++------------------------------
 2 files changed, 2 insertions(+), 37 deletions(-)

diff --git a/bsp-howto/miscellanous_support.rst b/bsp-howto/miscellanous_support.rst
index efb4454..015adb4 100644
--- a/bsp-howto/miscellanous_support.rst
+++ b/bsp-howto/miscellanous_support.rst
@@ -206,13 +206,6 @@ macros:
   stack size as recommended when using this BSP.  This is sometimes required
   when the BSP developer has knowledge of stack intensive interrupt handlers.
 
-.. index:: BSP_ZERO_WORKSPACE_AUTOMATICALLY
-
-- ``BSP_ZERO_WORKSPACE_AUTOMATICALLY`` is defined when the BSP requires that
-  RTEMS zero out the RTEMS C Program Heap at initialization.  If the memory is
-  already zeroed out by a test sequence or boot ROM, then the boot time can be
-  reduced by not zeroing memory twice.
-
 .. index:: BSP_DEFAULT_UNIFIED_WORK_AREAS
 
 - ``BSP_DEFAULT_UNIFIED_WORK_AREAS`` is defined when the BSP recommends that
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
index 36c7f15..81bc9bb 100644
--- a/c-user/configuring_a_system.rst
+++ b/c-user/configuring_a_system.rst
@@ -996,8 +996,8 @@ RANGE:
     Defined or undefined.
 
 DEFAULT VALUE:
-    This is not defined by default, unless overridden by the BSP.  The default
-    is *NOT* to zero out the RTEMS Workspace or C Program Heap.
+    This is not defined by default.  The default is *NOT* to zero out the RTEMS
+    Workspace or C Program Heap.
 
 DESCRIPTION:
     This macro indicates whether RTEMS should zero the RTEMS Workspace and C
@@ -3187,34 +3187,6 @@ NOTES:
     only impacts the devFS and thus is only used by ``<rtems/confdefs.h>`` when
     ``CONFIGURE_USE_DEVFS_AS_BASE_FILESYSTEM`` is specified.
 
-.. index:: BSP_ZERO_WORKSPACE_AUTOMATICALLY
-
-.. _BSP_ZERO_WORKSPACE_AUTOMATICALLY:
-
-BSP_ZERO_WORKSPACE_AUTOMATICALLY
---------------------------------
-
-CONSTANT:
-    ``BSP_ZERO_WORKSPACE_AUTOMATICALLY``
-
-DATA TYPE:
-    Boolean feature macro.
-
-RANGE:
-    Defined or undefined.
-
-DEFAULT VALUE:
-    This option is BSP specific.
-
-DESCRIPTION:
-    If ``BSP_ZERO_WORKSPACE_AUTOMATICALLY`` is defined by the BSP and
-    ``CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY`` is not defined by the
-    application, then the workspace will be zeroed automatically.
-
-NOTES:
-    Zeroing memory can add significantly to system boot time. It is not
-    necessary for RTEMS but is often assumed by support libraries.
-
 .. index:: CONFIGURE_BSP_PREREQUISITE_DRIVERS
 
 .. _CONFIGURE_BSP_PREREQUISITE_DRIVERS:



More information about the vc mailing list