Why sound isn't working on the TP2.

[YnYng]

i believe variance hired some freelancers, but havent seen him around in a bit

[Lioric HTC]

Originally Posted by jonpry

That sounds like a working theory . My understanding is that the GPU is actually some code running on the DSP. So if DSP is crashed or something, sound and 3d wouldn't work.

Do you have a link or something to a reference about the Adreno being some code in the DSP? (not sarcasm, actually I'm interested in any information about the GPU that we can collect)

From the little available information the Adreno GPU (ATI Imageon) used in our devices is a SoC that happens to have a (dual?) DSP (for audio and video), to me that tells me that the GPU is an actual hardware subsytem and not just some code in the DSP

With that being said, I have the feeling that when we have a working sound, we will automatically have a working GPU (in terms of interrupts), as what it seems is that the audio is handled by one of those dsp's (or an Imageon Mx audio processor)

Im waiting for my Omap DM3730 (with SGX GPU) SoC, after that arrives I will start working on it and will do the some jtag, and then will test Android on that, Im very tempted to do that on the tp2, just not sure that I want to solder my phone (when actually is the only tp2 in my country)

Anyway, it might be of some help if the guy that was debugging with jtag on his phone publishes the pins and the logic level used

If I try that I will prob test it with a Flyswatter interface, hope the ARM11 is somewhat supported

Wish there was a complete msm7600 datasheet available

[[ACL]]

Originally Posted by Lioric HTC

Do you have a link or something to a reference about the Adreno being some code in the DSP? (not sarcasm, actually I'm interested in any information about the GPU that we can collect)

From the little available information the Adreno GPU (ATI Imageon) used in our devices is a SoC that happens to have a (dual?) DSP (for audio and video), to me that tells me that the GPU is an actual hardware subsytem and not just some code in the DSP

With that being said, I have the feeling that when we have a working sound, we will automatically have a working GPU (in terms of interrupts), as what it seems is that the audio is handled by one of those dsp's (or an Imageon Mx audio processor)

Im waiting for my Omap DM3730 (with SGX GPU) SoC, after that arrives I will start working on it and will do the some jtag, and then will test Android on that, Im very tempted to do that on the tp2, just not sure that I want to solder my phone (when actually is the only tp2 in my country)

Anyway, it might be of some help if the guy that was debugging with jtag on his phone publishes the pins and the logic level used

If I try that I will prob test it with a Flyswatter interface, hope the ARM11 is somewhat supported

Wish there was a complete msm7600 datasheet available

you are correct, the gpu itself is one of the ATI imageon chips. However, the topaz and rhodium are the only ones with no interrupts for the gpu. Others already have this working like Blackstone and Kovsky.

We have very little info on the gpu itself. Just what's been already documented by research others have done already and through disassembly of most of the oem drivers. I have a post on here about the open gl, but we dont really discuss the hardware.

I believe the pins themselves were already published a while back by others. I know i posted a link on xda about it, ill research and post it here when i find. it.

[jonpry]

http://www.khronos.org/developers/li...GLES-Astle.ppt

It's a bit of a stretch, and potentially old .

[Lioric HTC]

Actually that document shows that the GPU on the tp2 is complete hardware path (Convergence platform -> tp2), not DSP based, but what is interesting is that in the other platforms it shows the DSP being used for audio (additionally of MV and other transformations, light, color and clipping) and that the dsp is used (to external SRAM) for double buffering

Hope to have my android dev environment ready soon

[daddymikey1975]

I was looking at the HTC hero specs.. I noticed that the processor model and speed are the same as the TP2..

Without knowing much about the internals of both devices (beyond what I read on HTC's website) would we be a step ahead if we were to look into the android build for the Hero ??

Would that help us w/ the TP2 at all ?

Just wondering..

[[ACL]]

Originally Posted by daddymikey1975

I was looking at the HTC hero specs.. I noticed that the processor model and speed are the same as the TP2..

Without knowing much about the internals of both devices (beyond what I read on HTC's website) would we be a step ahead if we were to look into the android build for the Hero ??

Would that help us w/ the TP2 at all ?

Just wondering..

If we have gone as far as disassembling the windows dlls, i can assure you we have examined every kernel you can get your hands on.

[[ACL]]

Originally Posted by jonpry

http://www.khronos.org/developers/li...GLES-Astle.ppt

It's a bit of a stretch, and potentially old .

How far did you get on making rpc calls related to audio? I know you were successful with the gps obviously but i haven't been able to make any calls. One example was trying to enable grp rail via rpc (A9 would crash).

[Lioric HTC]

I was looking at the HTC hero specs.. I noticed that the processor model and speed are the same as the TP2..

What might be better is to completely remove android and start with a slim linux with no other modules other than the bare libs modules needed to boot and start a test 3d application (just to load and ping the gpu), then we can trace what is clicking and what not between both units

[[ACL]]

Originally Posted by Lioric HTC

What might be better is to completely remove android and start with a slim linux with no other modules other than the bare libs modules needed to boot and start a test 3d application (just to load and ping the gpu), then we can trace what is clicking and what not between both units

Thats what we already have. Nothing to do with the hero...

Linux itself doesnt show any interrrupts for hw3d. Once again nothing to do with android.