Nu... your comments lead me to believe that you think the device is using eXecute In Place. I'm not sure if you read my NOR/NAND thread, but at this point I don't believe the Kaiser is using NOR RAM. This means that there is nothing that is XIPing directly off the ROM. The contents of the XIP are preloaded into RAM to act as a "XIP cache" if you will.
I'm only remarking, as I understand it, everything from the xip, as seen in the Part01.raw ROM dumps, is intended to run from any available NOR ram to XIP. The fact the Part01.raw dump is 5MB strongly suggests this, but as to how HTC actually implemented it on the Kaiser is up in the air.
Since, the OS kernel and many core subsystems exist in this 5MB section and the OS doesn't change (much), it's difficult to disbelieve that HTC wouldn't at least try to implement some XIP nvram in order to save battery.
But yes, this is all beside the topic which is what is a good size to set the pagepool to.
I agree excuse my rude behavior, for not thanking you for your time and effort. I too am using a 16mb pp and it seems to work on Dutty's 19209 Build.
Sometimes when I get issues like that I re-flash the radio. I don't know why this helps, but I noticed when flashing a lot of the times changing the pagepool, I never changed my radio from 126.96.36.199. I would get random freezes like you said re-flash the radio and the problems would go away.
Anyways Great Job my friend
|Thread Tools||Search this Thread|