In message <1238023305.18642.45.ca...@duiker>
John-Mark Bell <[email protected]> wrote:
> How much processing would be required on the ELF-wrapped module to get
> it in a format RO will cope with? Is it overly naive to hope that it's
> simply a case of calling the "load module from memory" OS_Module reason
> code with an appropriate offset into the memory-resident binary?
Not at all naive IMHO: it wouldn't surprise me that the two loadable
ELF sections (RO & RW) are already located after each other in the
ELF file so if you would place the ELF file in an RMA block, you could
just link in the embedded module part like that (just a temporary (?)
word value overrule is needed before where the module starts as that
defines the module's length).
But note that according the ELF headers, the module binary data is
loaded at 0x8088 (I think) so some fiddling is probably required to make
sure it realises that it is loaded elsewhere.
John.
--
John Tytgat, in his comfy chair at home BASS
[email protected] ARM powered, RISC OS driven
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
