summaryrefslogtreecommitdiffstats
path: root/c/src/lib/libbsp/m68k/ChangeLog
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>2008-05-15 15:52:15 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>2008-05-15 15:52:15 +0000
commit621feee0620f8b1a037d2b7118013a75f1ca6508 (patch)
treecc52b6f777cd9feaef97a97563a1a49aa48ef123 /c/src/lib/libbsp/m68k/ChangeLog
parent2008-05-15 Joel Sherrill <joel.sherrill@OARcorp.com> (diff)
downloadrtems-621feee0620f8b1a037d2b7118013a75f1ca6508.tar.bz2
2008-05-15 Joel Sherrill <joel.sherrill@OARcorp.com>
* shared/m68kpretaskinghook.c: Add capability for bootcard.c BSP Initialization Framework to ask the BSP where it has memory for the RTEMS Workspace and C Program Heap. These collectively are referred to as work area. If the BSP supports this, then it does not have to include code to split the available memory between the two areas. This reduces the amount of code in the BSP specific bspstart.c file. Additionally, the shared framework can dirty the work area memory. Until most/all BSPs support this new capability, if the BSP supports this, it should call RTEMS_BSP_BOOTCARD_HANDLES_RAM_ALLOCATION from its configure.ac. When the transition is complete, this autoconf macro can be removed. * shared/m68kbspgetworkarea.c: New file.
Diffstat (limited to '')
-rw-r--r--c/src/lib/libbsp/m68k/ChangeLog15
1 files changed, 15 insertions, 0 deletions
diff --git a/c/src/lib/libbsp/m68k/ChangeLog b/c/src/lib/libbsp/m68k/ChangeLog
index 91fcd6a2b3..2fa27436d2 100644
--- a/c/src/lib/libbsp/m68k/ChangeLog
+++ b/c/src/lib/libbsp/m68k/ChangeLog
@@ -1,3 +1,18 @@
+2008-05-15 Joel Sherrill <joel.sherrill@OARcorp.com>
+
+ * shared/m68kpretaskinghook.c: Add capability for bootcard.c BSP
+ Initialization Framework to ask the BSP where it has memory for the
+ RTEMS Workspace and C Program Heap. These collectively are referred
+ to as work area. If the BSP supports this, then it does not have to
+ include code to split the available memory between the two areas.
+ This reduces the amount of code in the BSP specific bspstart.c file.
+ Additionally, the shared framework can dirty the work area memory.
+ Until most/all BSPs support this new capability, if the BSP supports
+ this, it should call RTEMS_BSP_BOOTCARD_HANDLES_RAM_ALLOCATION from
+ its configure.ac. When the transition is complete, this autoconf
+ macro can be removed.
+ * shared/m68kbspgetworkarea.c: New file.
+
2007-12-11 Joel Sherrill <joel.sherrill@OARcorp.com>
* shared/m68kpretaskinghook.c: Eliminate copies of the Configuration