On Thu, 23 Oct 2008 14:50:33 +0530 "ext naveen krishna ch" <naveenkrishna.ch@xxxxxxxxx> wrote: > > So to summarize: > > > > - 2.6.26 + backported drivers on OMAP3 EVM -> audio works > > - 2.6.26 + backported drivers on custom board with NAND boot -> no audio > > - 2.6.26 + backported drivers on custom board with MMC boot -> audio > > works > > - 2.6.24 (TI SDP release?) on custom board -> audio works > > > > And I understood also that bootloader images were the same in all of > > these cases. Did I get these correctly? > > > Yeah till here u got every thing correctly. > Then it looks that different pin muxing is not the reason if the same bootloader images behave differently when they are booted from NAND vs. MMC. I'm bit out of idea what might then cause that audio doesn't play. Timing issue? Sys.boot pin states affect McBSP muxing or TWL4030, etc? > > Is the rootfile system the same between these cases? I.e. that same > > mixer settings like audio volumes etc. are used? > > i Have used the same root file system also that too over nfs all the cases. > Ok. Is it possible you to try with up-to-date linux-omap [1] kernel? There have been lot of changes regarding OMAP3 and TWL4030 since 2.6.26 so problem might have gone and then it's easier for others trying to verify problem on other similar boards. Jarkko [1] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git or http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
