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

2008-09-17 Joel Sherrill <joel.sherrill@OARcorp.com>

Browse Source 
* user/conf.t: Fix typo.
This commit is contained in:
Joel Sherrill
2008-09-17 19:03:10 +00:00
parent 1117465116
commit 96a0303b63
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/ChangeLog
View File

@@ -1,3 +1,7 @@
2008-09-17 Joel Sherrill <joel.sherrill@OARcorp.com>
* user/conf.t: Fix typo.
2008-09-17 Joel Sherrill <joel.sherrill@oarcorp.com> 2008-09-17 Joel Sherrill <joel.sherrill@oarcorp.com>
* user/conf.t: Add support for optionally having a unified work area. * user/conf.t: Add support for optionally having a unified work area.

2
doc/user/conf.t
View File

@@ -214,7 +214,7 @@ of the RTEMS RAM Workspace.
@item @code{CONFIGURE_UNIFIED_WORK_AREAS} configures RTEMS to use a @item @code{CONFIGURE_UNIFIED_WORK_AREAS} configures RTEMS to use a
single memory pool for the RTEMS Workspace and C Program Heap. If not 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 defined, there will be separate memory pools for the RTEMS Workspace and
C Program Heap. Having separate pools does haved some advantages in the C Program Heap. Having separate pools does have some advantages in the
event a task blows a stack or writes outside its memory area. However, 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 in low memory systems the overhead of the two pools plus the potential
for unused memory in either pool is very undesirable. for unused memory in either pool is very undesirable.