diff options
| author | Jeff Johnston <jjohnstn@redhat.com> | 2015-05-26 15:30:30 -0400 |
|---|---|---|
| committer | Corinna Vinschen <corinna@vinschen.de> | 2015-05-27 13:30:20 +0200 |
| commit | 5eb4a1666dffbeb3e823d5372c603ac930e6ba9f (patch) | |
| tree | 9dc9f9630f2ecf10e340401433e5d367de4594ea /lt~obsolete.m4 | |
| parent | 58efeedd1670555d4eadf23309122fd6aa64c9b2 (diff) | |
| download | newlib-5eb4a1666dffbeb3e823d5372c603ac930e6ba9f.zip newlib-5eb4a1666dffbeb3e823d5372c603ac930e6ba9f.tar.gz newlib-5eb4a1666dffbeb3e823d5372c603ac930e6ba9f.tar.bz2 | |
or1k: set heap start for optimsoc-gzll
- With the gzll kernel we have two different loading options:
- If the image is loaded to the global memory, the bootstrapping
loads the kernel to local memory. Applications are loaded on
demand. The heap then starts right after bss.
- If the image is pre-loaded to the local memory it includes the
application binaries right after bss. The heap then starts after
the application objects.
- We can check if this is a gzll kernel as it has the string "gzll" at
0x2000. At 0x200c we then find the end of the application objects in
the image. If there is no global memory we set _or1k_heap_start to
this value.
* or1k/boards/optimsoc.S: Heap for gzll kernel
Diffstat (limited to 'lt~obsolete.m4')
0 files changed, 0 insertions, 0 deletions