On Thu, Oct 25, 2012 at 12:49 AM, Omar Ramirez Luna <[email protected]> wrote:
> On Wed, Oct 24, 2012 at 10:34 AM, Felipe Contreras > <[email protected]> wrote: >> Selso, hopefully you don't mind, but I'll forward this to the >> linux-omap mailing list, as this seems to be an interesting kernel >> problem in tidspbridge. >> >> Omar, any ideas? > > I don't see tidspbridge trace paths (but I don't discard something > wrong either ;)), however I do see a framebuffer, dss, dispc trace, > might be a good point to start checking: Oops, you are right. >>> CONFIG_TIDSPBRIDGE_CACHE_LINE_CHECK=y > > I wasn't aware that now gst-dsp supported this, might be time to update mine. Yes, it's supported now. Took me a lot of changes to manage to do it, but it's there. > Anyway, right now I have lots of debugging enabled and specifically > the one that spits "scheduling while atomic" with kernel 3.7-rc2, and > I'm not seeing this with the fakesink decode, and the encoder to a > file, I don't have framebuffer nor display though. It's probably a framebuffer problem =/ -- Felipe Contreras -- 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
