From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id DDCCBDDEF0 for ; Tue, 28 Apr 2009 06:50:05 +1000 (EST) Message-ID: <49F61A77.4060404@freescale.com> Date: Mon, 27 Apr 2009 15:49:59 -0500 From: Timur Tabi MIME-Version: 1.0 To: Scott Wood Subject: Re: [PATCH] fsldma: use PCI Read Multiple command References: <20090424183517.GB23140@ovro.caltech.edu> <49F608B7.9080409@ovro.caltech.edu> <49F60A3A.4060402@freescale.com> <49F60BF8.8040404@ovro.caltech.edu> <49F60FE1.90707@freescale.com> <20090427204752.GA22406@ld0162-tx32.am.freescale.net> In-Reply-To: <20090427204752.GA22406@ld0162-tx32.am.freescale.net> Content-Type: text/plain; charset=ISO-8859-1 Cc: David Hawkins , Ira Snyder , Liu Dave-R63238 , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Dan Williams List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Scott Wood wrote: > I thought the driver only used the bit if the device tree indicated it > was an 83xx-era DMA controller? I just wanted to make sure it didn't do anything weird. It was the only test I could think of that didn't involve PCI. > That said, the bits are documented as specifically for PCI, so it would > be surprising if it had any effect elsewhere. Surely you wouldn't really be surprised by incorrect documentation of our parts. :-) -- Timur Tabi Linux kernel developer at Freescale