Quote:
Originally Posted by dan-htc-touch
from what I can tell, the reason for having a xip section, is to make it possible to handle the xip in a different way.
excerpt from MSDN:
Windows CE allows you to create multiple execute in place (XIP) regions in one single operating system (OS) image. XIP regions are areas where an application can execute code directly from read-only memory (ROM) rather than having to load it from random access memory (RAM).
With a multi-region image, you have finer control over the image layout, you can control region updates, and you can decide on a per-region basis how the OS will access that region when it pages its components at run time.
|
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?