Reclaim .iram areas in DRAM by overlapping their load addresses with the uninitialized data sections. I did what I could test out-- not any flash image linker scripts or other target processors. Move any .iram copies in crt0.S's to be the first operation even if not _strictly_ necessary to be emphatic (aka. 'beware').

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@20061 a1c6a512-1295-4272-9138-f99709370657

1 files changed, 2 insertions, 2 deletions

diff --git a/firmware/target/arm/olympus/app.lds b/firmware/target/arm/olympus/app.lds
index d7159e8e1e..22468192eb 100644
--- a/firmware/target/arm/olympus/app.lds
+++ b/firmware/target/arm/olympus/app.lds
@@ -103,6 +103,7 @@ SECTIONS
     } AT> DRAM
 
     _vectorscopy = LOADADDR(.vectors);
+    _noloaddram  = LOADADDR(.vectors);
 
     .ibss IRAMORIG (NOLOAD) :
     {
@@ -148,8 +149,7 @@ SECTIONS
 
     /* .bss and .ncbss are treated as a single section to use one init loop to
      * zero it - note "_edata" and "_end" */
-    .bss ADDR(.data) + SIZEOF(.data) + SIZEOF(.ncdata) +\
-         SIZEOF(.iram) + SIZEOF(.vectors) (NOLOAD) :
+    .bss _noloaddram (NOLOAD) :
     {
        _edata = .;
         *(.bss*)