Quote:
Originally Posted by joojoobee666
I did just manage to come across this little tidbit:
"The advantage of XIP modules comes into play when one considers the limited amount of RAM available on a typical Windows Mobile device. XIP modules are pre-relocated to a guaranteed available base address, and do not require any runtime alterations to their backing memory when mapped. As a result, XIP modules can be backed entirely by ROM and not RAM, decreasing the (scarce) RAM that must be devoted to holding executable code"
So, if I am reading this correctly, it would be advantageous to convert ANY program/dll that needs to stay loaded/in use for the entire boot into a module. This should in essence free more RAM? (HTC Task Manager is one example, Arcsoft being another, and possibly even some phone/canvas related resources)
And just going one step further, the XIP layout is what WMreloc is actually doing. It is creating the imgfs and XIP maps?
|
yeah, wmreloc relocates modules memory mapping adreesses, so that there are no overlaps, converting to module can be good, but does not work for everything, basically, only program code can be xip, content cannot, so in the case of phone canvas, the core executable may be xip, the all the graphics will still reside in RAM, so the savings will not be huge