RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

minimum: Do not use unified work areas

Browse Source 
The CONFIGURE_UNIFIED_WORK_AREAS option pulls in a system initialization
handler which initializes the unified heap.

Close #4108.
This commit is contained in:
Sebastian Huber
2022-09-08 16:11:43 +02:00
parent 52d566c864
commit 120c857ea1
1 changed files with 0 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
testsuites/samples/minimum/init.c
View File

@@ -104,21 +104,6 @@ static void *Init( uintptr_t ignored )
*/
#define CONFIGURE_MAXIMUM_PRIORITY 15
/*
* This configures RTEMS to use a single memory pool for the RTEMS Workspace
* and C Program Heap. If not defined, there will be separate memory pools
* for the RTEMS Workspace and C Program Heap. Having separate pools
* does haved some advantages in the event a task blows a stack or writes
* outside its memory area. However, in low memory systems the overhead of
* the two pools plus the potential for unused memory in either pool is
* very undesirable.
*
* In high memory environments, this is desirable when you want to use
* the RTEMS "unlimited" objects option. You will be able to create objects
* until you run out of memory.
*/
#define CONFIGURE_UNIFIED_WORK_AREAS
/*
* In this application, the initialization task performs the system
* initialization and then transforms itself into the idle task.