Originally Posted by [ACL] (Post 1840823)

Here is a quick update. I havent solved the puzzle yet, but i have been working with some of the blackstone devs since they have a 3d issue as well. We figured comparing clock values would help. Turns out the dlls values on both black and rhod are identical. This is disappointing since i figured maybe the clocks were wrong and thats why it was not working.

.text:10004CE8 ; =============== S U B R O U T I N E =======================================
.text:10004CE8
.text:10004CE8
.text:10004CE8 sub_10004CE8 ; CODE XREF: sub_10004EC4+430p
.text:10004CE8 ; DATA XREF: .pdata:10008348o
.text:10004CE8 STMFD SP!, {R4,LR}
.text:10004CEC CMP R0, #0
.text:10004CF0 BEQ loc_10004DB8
.text:10004CF4 LDR R4, =unk_100071DC
.text:10004CF8 MOVL R1, 0x11F
.text:10004D00 LDR R2, [R4,#8]
.text:10004D04 MOV R0, #2
.text:10004D08 LDR R3, [R2,#0x208]
.text:10004D0C ORR R3, R3, #0x20
.text:10004D10 STR R3, [R2,#0x208]
.text:10004D14 LDR R2, [R4,#8]
.text:10004D18 LDR R3, [R2,#0x214]
.text:10004D1C ORR R3, R3, #0x20000
.text:10004D20 STR R3, [R2,#0x214]
.text:10004D24 LDR R3, [R4,#8]
.text:10004D28 STR R1, [R3,#0x284]
.text:10004D2C BL sub_10004CAC
.text:10004D30 LDR R2, [R4,#8]
.text:10004D34 LDR R3, [R2,#0x84]
.text:10004D38 ORR R3, R3, #0x800
.text:10004D3C STR R3, [R2,#0x84]
.text:10004D40 LDR R2, [R4,#8]
.text:10004D44 LDR R3, [R2,#0x84]
.text:10004D48 ORR R3, R3, #0x80
.text:10004D4C STR R3, [R2,#0x84]
.text:10004D50 LDR R2, [R4,#8]
.text:10004D54 LDR R3, [R2,#0x84]
.text:10004D58 ORR R3, R3, #0x200
.text:10004D5C STR R3, [R2,#0x84]
.text:10004D60 LDR R2, [R4,#8]
.text:10004D64 LDR R3, [R2]
.text:10004D68 ORR R3, R3, #8
.text:10004D6C STR R3, [R2]
.text:10004D70 LDR R2, [R4,#8]
.text:10004D74 LDR R3, [R2,#0x290]!
.text:10004D78 BIC R3, R3, #4
.text:10004D7C STR R3, [R2]
.text:10004D80 LDR R2, [R4]
.text:10004D84 LDR R3, [R2,#0x80]
.text:10004D88 BIC R3, R3, #1
.text:10004D8C STR R3, [R2,#0x80]
.text:10004D90 LDR R2, [R4,#8]
.text:10004D94 LDR R3, [R2,#0x208]
.text:10004D98 BIC R3, R3, #0x20
.text:10004D9C STR R3, [R2,#0x208]
.text:10004DA0 LDR R2, [R4,#8]
.text:10004DA4 LDR R3, [R2,#0x214]
.text:10004DA8 BIC R3, R3, #0x20000
.text:10004DAC STR R3, [R2,#0x214]
.text:10004DB0 LDMFD SP!, {R4,LR}
.text:10004DB4 BX LR

All those values above can be found on our kernel which now makes me think i have to look at something else. The weird thing is that when we dump clocks from haret, it does not match the above values .. lol so we have asm that is lying? or there is another call we are missing and not analysing . Whatever it is, the search continues.

Originally Posted by newkidd (Post 1844071)

what about tricking the 3d chip. if 3d was activated through a program that activated hw3d, then booted haret, tell android that hw3d is already initialized, then give it the call to turn it off.

since im backtracking through the IRC logs and everything else i dont know what you have tried and havent tried.

Originally Posted by veeeee (Post 1850594)

I compared the blackstone ddi.dll to the rhodium ddi.dll and there are differences. I am attaching the .dll's in case you want to inspect them yourself.

Originally Posted by [ACL] (Post 1851588)

how do i see these files ? i see just bunch of s00X stuff.. i need the dlls itself.

Originally Posted by [ACL

]Once haret loads, wince is no longer in-charge of the device. We must enable and disable everything.. kernel starts loading and it loads the appropriate drivers.

Originally Posted by newkidd (Post 1851965)

ill pull them both apart and see if there are any major differences worth finding. ive been needing to boot back to windows and reformat a hard drive to use on my Wii, i was just looking for a reason :)


so the interrupts were already in place? thats a positive, although it confuses me. was it not already running in wince?

i was thinking the other day, probably going around in circles, but it made me wonder on something you said.



so what happens on other devices, where we had to make a phone call and then boot haret. was it much easier to initiate phone audio with it already "running" or what?

also, can you do me a favor whenever you get the chance? can you send me some logs in wince when you are doing several procedures? initiate a game that uses hw3d, a game that doesnt activate 3d, and when playing back a video recorded by the phone through windows media player.

just looking at a few things, but really anyone can do this. what would really help is to get the boot logs from several native android devices, and maybe some logs using hw3d. it really doesnt matter which device, as essentially initiating the drivers and calling them should correlate.

Originally Posted by [ACL] (Post 1852052)

Well, phone call stuff works since its all done by A9. we really dont need ot do anything. Its handled internally. Things like 3d, need calls to be made to enable and disable it.

Android devices are completely different. For example all their clocks are also handled internally not like wince that has to set its own stuff. So once haret boots, no one is there to handle it any-more. I'm interested to see what would happen with a Rhod that has no 3d. We have everything in theory ready to turn on 3d, maybe the fact that its enabled messes it up. Dont know at this stage

Wince logs are useless. But here is a full boot log to show you what happens as soon as the device turns on, to when it begins activating 3d for manila.

http://pastebin.com/M1Ad4YMv

Also i put my own debug lines on the kernel to get more logging. So logs from android devices wont help since they dont tell the whole story.

Originally Posted by newkidd (Post 1852268)

i was mainly trying to get the wince logs for my personal uses, but i can grab it whenever i boot back over to ubuntu.

what else uses the 3d chip? maybe something is configured wrong with the setup and its keeping the calls from working?

Originally Posted by [ACL] (Post 1852291)

Well.. Manila has 3d wide open. its always on. If you turn off 3d, then manila becomes useless. It would be nice if we had someone with a vanilla rom who can try out 3d. Im wondering if having it enabled is causing the issue.

As a test i ran haret with the lcd off since thats when everything is off. Android doesnt boot. It loops because 3d on the animation screen tries to wake up the lcd but it cant.

Originally Posted by WoZZeR999 (Post 1852422)

You can try just disabling Manila as a today plug-in. That should keep it from starting up. That might help you out. I can also find a sprint rom and cook you a HTC-less rom.

Originally Posted by kroewe (Post 1852529)

i turned off sense/manila and adroid wouldnt boot at all
tried several different times, switching back to sense it would boot, disable it, wont boot.

Originally Posted by WoZZeR999 (Post 1854402)

I'll run some tests tomorrow. I'm assuming this rom: RaidZero*Android Loader does not have manila on it, so it should not make a difference.

Originally Posted by [ACL] (Post 1854342)

Thats odd. I disabled manila (i think i did at least) and put the default winmo crap and my android still boots. Did you guys do anything different? Do i actually have to remove sense out of the phone. I'm interested in seeing why it does not load for you guys.

Originally Posted by [ACL] (Post 1854342)

Thats odd. I disabled manila (i think i did at least) and put the default winmo crap and my android still boots. Did you guys do anything different? Do i actually have to remove sense out of the phone. I'm interested in seeing why it does not load for you guys.

Originally Posted by newkidd (Post 1854911)

i was running maxsense (bignadad's rom), but i flashed NRG's max sense and it did the same thing.

what rom are you running?

maybe the clocks are set with the idea that hw3d is already enabled, however if hw3d isnt already enabled and running, it crashes because the clocks arent right for that session?

Originally Posted by [ACL] (Post 1856087)

Hard to say .. without logs, i cant tell why its not working for you.

Here is an idea. Can you dump your clocks with haret? we can compare to see what your rom does different than the manila one.

Originally Posted by newkidd (Post 1856620)

sure!


...how exactly do i do that with haret?

Originally Posted by [ACL] (Post 1854342)

Thats odd. I disabled manila (i think i did at least) and put the default winmo crap and my android still boots. Did you guys do anything different? Do i actually have to remove sense out of the phone. I'm interested in seeing why it does not load for you guys.

Originally Posted by NeoMatrixJR (Post 1856965)

do they have the cmdline option to enable hw3d? I *think* if you enable it in startup.txt, but shutdown manilla (3d in WinMo) you have this problem.

Originally Posted by [ACL] (Post 1858539)

ive been testing and i guess i can replicate your error if i launch haret with the lcd off or if reset clocks early in the kernel. Part of the issue i think is we rely heavily on how Wince leaves the state of the clocks. So we need to learn how to check all of these and enable them if they arent where they supposed to be

Originally Posted by [ACL] (Post 1867629)

haven't been able to put time in this week. Anyone at least get their kernel up ? lol

i rewrote most of wince-clocks based on the outputs i get from dumping the clocks from wince. I know our code matches the asm 100 percent but it doesnt match what we dump. So i wrote it to match what we have in the current code and so far still no irqs. So i think its no longer a clock or grp rail issue. We are in fact enabling grp rail since the bits match wince.

Originally Posted by Lioric HTC (Post 1874307)

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?

Originally Posted by [ACL] (Post 1861577)

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 ..

Originally Posted by Lioric HTC (Post 1884594)

yep, vs2008 + 6.5 sdk