Hi all,

Turns out my recent DMA changes broke omap1 dma to some extent.
I've pushed a fix for that, and also a fix for old alsa code,
and a compile fix for H4.

I also fixed omap_get_dma_src/dst_pos() to return the current
address. So if there are still some old drivers (wrongly) assuming
this function returns the transfer count, they're even more broken
now. Please everybody check your drivers for that.

It also seems that omap3430sdp ES2.0 returns 0 for CDAC address.
This means omap_get_dma_dst_pos() will always return 0, which
may break some drivers..

I have no idea why CDAC is 0 on 3430, there's something in TRM in
"9.5.4 Synchronized Transfer Monitoring Using CDAC" about setting
CDAC, but so far no luck. Maybe this only works for hardware triggered
transfers?

If anybody has ideas why CDAC is not behaving let me know!

Cheers,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to