Quote:
Originally Posted by [ACL]
Found out why its bombing out when manila is disabled. Once you disable it 2 values in memory change.
0xA860010C and 0xA8600084
However, once you reboot it looks like the values return to how they should be. I still yet to find out why its crashing. I did notice that if you shut down manila, and you run a 3d app, the values fix themselves.
The actual call that crashes the system is the get_clk_khz(); in the clock_late_init. This call is somewhat useless right now so i commented it out on my kernel and was able to boot.
Unfortunately none of this got 3d working. The hunt continues ..
|
more or less it sounds like clocks are set with 3d boot already enabled, and its doing a hand off.
ill more or less be your testing peon as soon as my new hard drive shows up. one i had got left behind in the move then damaged during shipping to me.
__________________
WM 6.5 may be being phased, but the heartbeat of the windows mobile community is like a heard of elk.
*edit*
Actually the windows mobile community is more like a rabbit family than a heard of elk. all it takes is a slight bit of action and next thing you know theres a million of them.