From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <469E7350.3090308@freescale.com> References: <20070718013137.GA15217@ld0162-tx32.am.freescale.net> <20070718013611.GY15238@ld0162-tx32.am.freescale.net> <20070718032857.GF18251@localhost.localdomain> <469E7350.3090308@freescale.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <97B4A805-6E2A-4F8E-BC56-5BDEE8D6F5F0@kernel.crashing.org> From: Kumar Gala Subject: Re: [PATCH 53/61] 82xx: Set NOT_COHERENT_CACHE on 8272 with PCI. Date: Thu, 19 Jul 2007 09:58:01 -0500 To: Scott Wood Cc: linuxppc-dev@ozlabs.org, David Gibson List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Jul 18, 2007, at 3:08 PM, Scott Wood wrote: > Kumar Gala wrote: >> On Jul 17, 2007, at 10:28 PM, David Gibson wrote: >>> Hrm... I for one would be a lot more comfortable with this patch if >>> you had a theoretical explanation for why it's necessary, in >>> addition >>> to the "seems to fix things". > > Sure, so would I; I just wanted to point out the issue, and make > available a quick fix for anyone else that might be having problems. > > My theoretical explanation is that the hardware is broken. :-P > >> I agree w/David. Have you tried turning on the >> CPU_FTR_NEED_COHERENT? Take a look at include/asm-powerpc/ >> cputable.h and search for the reference to CONFIG_PPC_83xx. > > OK, that appears to work as well. Can you dump the POCMRx registers and report their values and what / proc/iomem looks like. - k