[Touch Pro2, Tilt 2 Android Development] HeXeD:
Looks like there is some progress that I have no heard of that people might find interesting.

___________________________________________________

9:44 WisTilt2 [acl] hey, phh said you might be the guy to help troubleshoot some of the adsp irq issues to save us having to repeat what you may have already done?

19:46 WisTilt2 we have the ints working now but there's a problem in the ADSP_RTOS areas that we are going through line by line right now. Something isn't jiving with the memory mapping to the control registers.

19:48 [acl] WisTilt2: yeah im the poor soul

19:48 [acl] WisTilt2: well actually im just 3d.. Jonpry is the adsp guy

19:49 [acl] WisTilt2: both suffer the same issue. No interrupts. So any advice could help

19:49 WisTilt2 ah... you have 3d working on rhod? looks like a similar irq issue there also.

19:49 [acl] WisTilt2: no irqs on rhod

19:49 [acl] Same issue

19:50 WisTilt2 yeah this chipset is different than none rhod devices. we are looking at the memory mapping right now and something isn't right. the dsp isn't being setup correctly, even though it might appear it is.

19:52 [acl] WisTilt2: so the same is happening for 3d? mem mapping issue?

19:52 WisTilt2 [acl]: yes i believe so, although we haven't really dug into that much, just sound. do you happen to know what memory region the 3d is using?

19:53 [acl] in wince ?

19:54 [acl] i know i have all that info at home. I did try to one time map the wince addresses close to our pmem addresses. But even with messed up memory we should have irqs

19:55 WisTilt2 negative, that will probably be different. really don't know who or how they picked these mapped addresses that are being used in android.

19:57 [acl] WisTilt2: we tried different addresses. I even tried mapping them close to the wince addresses. Or used other devices as reference to map it in a similar way. This is where we gave up on mem issue. Since it yielded no results

19:58 Pedro- does Cotulla password his zImages now?

20:00 WisTilt2 [acl]:well at least in the adsp setup, the irqs arent working because the dsp never sees the correct command to enable it. we made a very stripped down kernel and started from there and got irq working. problem now is the dsp never seems to have a new message ready to read even though it generates the int saying it does.

20:01 [acl] ohh man i need to get a hold of jonpry and let him know the news. He has been bashing his brain against this sound issue

20:02 WisTilt2 [acl]:it's just a matter of going through line by line:) something is way off in the memory pointers for the command buffer. found several 16bit pointers that MUST be 32bit.

20:03 [acl] WisTilt2:ahhh .. ic..

20:03 WisTilt2 what timezone is jonpry in? i beat phh up enough on this stuff and he's 9hrs from us. we're in calif.

20:04 [acl] im in NY. I'll shoot jonpry an email.

20:05 WisTilt2 well at least you're only 3hr diff, makes it easier to work combined in close timezones.

20:08 WisTilt2 [acl]: btw, we have sound playing, however, it only plays less than 1/2sec. when the dsp generates the irq and the get_event is executed, the dsp always says there is no message ready so the next sound block is never filled to the buffer. That's why im fairly sure the dsp isn't config'd correctly and it's getting lost memory wise.

20:09 WisTilt2 ill bet the 3d issue is the same

_________________________________________

1/2 seconds of sound sounds better than no seconds of sound. Hopefully they can crush this issue and it sounds like 3D would be soon to follow if they get sound working.

Thanks to the devs for continuing to fight the good fight. ACL, jonpry, WisTilt2, phh..etc..etc