Quote:
Originally Posted by jakdillard
well my rom will not boot on a vzw tp (for now) my guess is that this has something to do with two modules I moved into imgfs (ddi.dll and gxdma.dll) so with the vzw tp YOU will have to do a trial and error thing as far as speeding up a rom THERE IS NOTHING THAT SPEEDS UP THE ROM OUTSIDE OF PAGEPOOL HACKING you can move modules out to downsize and gain some not alot in most cases in ram and gain in rom .... there are shorcuts to porting xip honestly its not rocket science like some like to make it out to be ...... lets say you have a have a Official GSM TP ROM ... cut the xip section from the rom decompile it repackage and from your Original CDMA xip move the OEMkernal to the new xip reallocate look for the overlapping modules (may be one or two) correct and BAM new xip .... or lets say you have a mogul and you want to port the updated official kaiser os to it well in this case just move the MSXIPKernal to the mogul OEMKernal reallocate then WOW xip ported .... xip porting can be simple for those that just want the numbers to match but more complicated for those who want performance its all in what you want
|
First, I have to disagree that pagepool is the only thing that speeds up a ROM. I do agree that it is the biggest bang for the buck. But a correctly implemented file filter cache does seem to be helping. Then there's making modules out of static DLLs and EXEs (well, speeds up load but not execute).
And the XIP port I did was basically exactly as you describe, however there were more than one or two modules overlapping, and quite a bit of free space - it took a lot of time to remove the overlap and decompress out the free space. In the end I don't think it was worth it - not that much was gained in terms of recovered RAM. BTW - I did remove the debug drivers and other items that the experts remove - just kept mencfilt.dll and cachefilt.dll.
My XIP map attached so you can see what is left and where, if interested.