On Mon, Aug 03, 2009 at 10:36:38AM +0200, ext Jarkko Nikula wrote: > On Mon, 3 Aug 2009 11:11:07 +0300 > Eduardo Valentin <eduardo.valentin@xxxxxxxxx> wrote: > > > > True, but I was wondering can this same problem occur also on McBSP2 if > > > using proper size threshold? Like size near the McBSP2 audio buffer > > > (1024x32) or near the TX buffer (256x32). > > > > Yes, it can happen with mcbsp2 also if you use all places (1024+256). > > > So should the patch then take into account McBSP2 also? hmmm.. But I've seen the problem only if you use 1024+256 for mcbsp2 (0x500) or very close to that (0x4F0). I haven't seen this problem using 0x3FF, as currently is. > > -- > Jarkko > -- > 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 -- Eduardo Valentin -- 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
