From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 7BA70DDDEE for ; Tue, 28 Apr 2009 05:56:37 +1000 (EST) Message-Id: <46B638E2-885C-4281-81EA-CB685264E143@kernel.crashing.org> From: Kumar Gala To: David Hawkins In-Reply-To: <49F60BF8.8040404@ovro.caltech.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: [PATCH] fsldma: use PCI Read Multiple command Date: Mon, 27 Apr 2009 14:54:22 -0500 References: <20090424183517.GB23140@ovro.caltech.edu> <49F608B7.9080409@ovro.caltech.edu> <49F60A3A.4060402@freescale.com> <49F60BF8.8040404@ovro.caltech.edu> Cc: Ira Snyder , Liu Dave-R63238 , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Dan Williams , Timur Tabi List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Apr 27, 2009, at 2:48 PM, David Hawkins wrote: > Can you give me an example of non-PCI memory that would be > non-prefetchable that you'd like us to try? We can see if our > host CPUs have an area like that ... we just need to know > what device to look for first :) You can mark the pci inbound window on the 83xx as non-prefetchable (assuming 83xx is host). On a x86 host I doubt there is any easy way to get non-prefetchable memory. - k