| commit | f8b70c98e3f396432c68e868b49910b99b2ae266 | |
| author | jethead71 <jethead71@a1c6a512-1295-4272-9138-f99709370657> | |
| Fri, 20 Feb 2009 02:33:40 +0000 (20 02:33 +0000) | ||
| committer | jethead71 <jethead71@a1c6a512-1295-4272-9138-f99709370657> | |
| Fri, 20 Feb 2009 02:33:40 +0000 (20 02:33 +0000) | ||
| tree | 8101f45d02947a828d20174a45d1a6d19fafa3b2 | treesnapshot (tar.gz zip) |
| parent | 976472e33735b5beda1c63e63d0d5d58dee33477 | commitdiff |
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
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@20061 a1c6a512-1295-4272-9138-f99709370657