Quote:
Originally Posted by Lioric HTC
if its not a grp rail or clk issue, are sure we have the correct amss? can't we flash other from a known hw3d working device to test and compare?
|
Correct amss? you wanna flash your phone be my guest
If you look at the clock dumps on the wiki vs the asm posted earlier, you will see that they really dont match up 100%. This is why clocks have been a concern for me.
If you have a dev env ready we can begin testing further (the more help the better). I havent been able to trace everything but i'm pretty sure about what ddi and ahi2dati does when initialising for 3d. DDI is just a wrapper for ahi2dati, when it's ready it calls the AhiInit function which will eventually call clk_regime_msm_enable and pass a value of 0x36 (enable grp). When you disect the clkregim.dll thats when all the clocks/rail are enabled. We posted that asm earlier.
What i havent done yet is actually get haret dumps when disabling and re-enabling via that function to see what other areas in memory are changed. I can write the app quickly, but i just dont have time to keep dumping and comparing the values.
Someone also suggested in maybe turning off the grp/rail before we launch android so we can enable it completely ourselves instead of relying on winmo to leave it enabled.