[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTikEmoFk89=jFtdgt-cKyRiJ2dkv49CV64bOOf1R@mail.gmail.com>
Date: Thu, 16 Sep 2010 11:59:03 +0900
From: venki kaps <venkiece2005@...il.com>
To: Felipe Contreras <felipe.contreras@...il.com>
Cc: Kevin Hilman <khilman@...prootsystems.com>, omar.ramirez@...com,
h-kanigeri2@...com, ameya.palande@...ia.com, fernando.lugo@...com,
x0hebbar@...com, ernesto@...com, s-anna@...com, grgupta@...com,
ivan.gomez@...com, ext-andriy.shevchenko@...ia.com,
x0095078@...com, deepak.chitriki@...com, nm@...com,
ext-phil.2.carmody@...ia.com, ohad@...ery.com,
devel@...uxdriverproject.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: OMAP3 DSP MMU fault + off mode issue
On Thu, Sep 16, 2010 at 7:34 AM, Felipe Contreras
<felipe.contreras@...il.com> wrote:
> On Wed, Sep 15, 2010 at 7:03 PM, venki kaps <venkiece2005@...il.com> wrote:
>> In latest kernels (Eg, linux-2.6.36-rc3),The MMU-Fault debugging
>> enhancements code is moved under CONFIG_TIDSPBRIDGE_BACKTRACE.
>
> Indeed, I added that configuration in order to avoid that possibly
> troublesome code in a production system. I haven't seen it working
> properly yet.
Thanks for the information.
Even I have not used that configuration but in production system, We
could avoid the DSP task information to be printed by the MPU
dspbridge when DSP MMU fault ocurrs.
Venkii,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists