It all depends on memory layout. I don't have those devices. Download
the tool, press system info and see list of heaps or regions. If palm
engineers were so clever that they packed heap and storage virtual
adresses next to each other and there are no holes in address space
before or after heap, nothing can be done. They have whole 4GB of
virtual memory space to use. But I know it may look nicer to developer's
mind to put it (uselessly) next to each other.
On NVFS devices I think there is also lot of RAM wasted for ROM image
padded to 8 or 16MB boundary. I wonder how big the rom really is and how
much ram is used for the image and wasted for padding. Such ram could be
used for bigger heap too instead of taking storage RAM. And if languages
could be removed from such ROM copy in ram (like JackFlash for flash),
there could be lot of memory free too.
And if ROM is in RAM anyway are there still two storage heaps
(1=ram,2=rom) or are they merged and writable?
BTW how FtrPtrNew work on NVFS devices? Is such memory allocated from
NVFS cache or is there separate area for this?
Frantisek
Henk Jonas wrote:
Hi Frantisek,
this sounds very interesting. Have you thought about doing the same with
current devices to bring more dynamic heap to Treo 650 or T5/X?
Regards
Henk
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
