Why sound isn't working on the TP2. - Page 26

WoZZeR999 · #**251** (**permalink**) 08-03-2010, 04:06 PM

[ACL], I'm downloading what I think is a 6.1 CDMA shipped rom right now, I'll post the XIP and OEMDrivers for you once it's done.

Here is the WM6.1 Sprint OEMDrivers and XIP

**[ACL]** · #**252** (**permalink**) 08-03-2010, 04:28 PM

Quote:

Originally Posted by WoZZeR999

[ACL], I'm downloading what I think is a 6.1 CDMA shipped rom right now, I'll post the XIP and OEMDrivers for you once it's done.

Here is the WM6.1 Sprint OEMDrivers and XIP

thanks man.. ill check it out. im hoping it's really different ..

WoZZeR999 · #**253** (**permalink**) 08-03-2010, 04:36 PM

I checked the Sprint 6.1 NK, and it still has the guarddog, but I don't see anything about masking the interrupt. So that is probably not causing the issue.

jonpry · #**254** (**permalink**) 08-03-2010, 11:18 PM

[acl]. i don't see what the point of pmem.c is. Looks like it is there so userland applications can have access to physmem that might move around between devices. Basically the same thing and wce_pmem.c. For sound, the only thing that would use it is htc_acoustic, which we don't have. qdsp5 driver finds its own memory and doesn't use pmem.

wce_pmem and wavedev are mapping in *lots* of phys mem. I count at least 5 16mb regions.

my technique of mmapping /dev/mem, doesn't require it. pmem is probably a prettier solution for when it works.

jonpry · #**255** (**permalink**) 08-04-2010, 12:57 AM

[acl]. i tried removing powermanagement support since i am going to be loading the wince one. Just having it removed gives me a dsp related int somewhere, although it still does not work. Also it is crashing my wce_pmem somehow. That is going to be tough to figure out.

2phonejones · #**256** (**permalink**) 08-04-2010, 11:33 AM

ur guys pockets will be LOADED when u get everything working ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh hhhhhhhhhhhhhhhhhhhhh

**[ACL]** · #**257** (**permalink**) 08-04-2010, 11:34 AM

jonpry : i tried the dzo irq changes. It doesnt break the build but it didnt help with 3d either. Replicating the VIC settings dont work too well either since our code disables them anyways. For example i left the 3d bit enabled but once hw3d.c loads, the bit gets disabled during init. I'm not sure if thats the case for all the devices.

jonpry · #**258** (**permalink**) 08-04-2010, 09:36 PM

[acl]. i don't think we should let anything enable or disable interrupts. We should just setup VIC just like WinCE and then ignore any calls to irq_enable or irq_disable other than hooking up the handlers. Presumably all the linux drivers will be requesting interrupts to get setup the way they already are anyways.

**[ACL]** · #**259** (**permalink**) 08-09-2010, 03:30 AM

Jonpry: There was some progress with the nand boot. Wozzer was able to boot but we are crapping out during the usb probe like expected.

compuw22c · #**260** (**permalink**) 08-09-2010, 09:50 AM

As relatively quiet as this thread has been (stuck to the topic very well!) I find it necessary to state the obvious and just say a HUGE thank you to everyone working so hard on all of this. Not just the sound, but the guys trying to install to NAND for us, the original devs that first got android to boot goofy touchscreen and all. Its guys (and girls) like you that make computers truly interesting. It's because of you that these devices are able to reach their true potential and I think its an absolute shame if you all don't end up in some very high-end programming or systems engineering job. I speak as someone who fixes computers frequently, servers, pcs, you name it, and am regarded as somewhat of a 'guru' around my friends and family, and I know full well your skills far FAR surpass mine.

Just figured a big thank you was in order. With talent like this, I know we'll get it eventually if it CAN be gotten.