From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Boyer Subject: Re: [PATCH] ata: libata depends on HAS_DMA Date: Tue, 12 May 2009 20:30:27 -0700 Message-ID: <20090513033027.GA13193@cynthia.pants.nu> References: <20090511222702.352192505@arndb.de> <200905112238.55404.arnd@arndb.de> <20090512090602.65722342@lxorguk.ukuu.org.uk> <200905121123.21436.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200905121123.21436.arnd@arndb.de> Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Arnd Bergmann Cc: Alan Cox , linux-kernel@vger.kernel.org, Jeff Garzik , linux-ide@vger.kernel.org, takata@linux-m32r.org, geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org, ysato@users.sourceforge.jp On Tue, May 12, 2009 at 11:23:20AM +0200, Arnd Bergmann wrote: > Currently, the only architectures that don't set HAS_DMA are h8300, m32r > m68k (except SUN3 and Coldfire), microblaze and s390. > s390 will never get it, microblaze is currently implementing dma-mapping.h. > > The other three are still using drivers/ide instead of drivers/ata. > > One way to fix this would be to implement dma-mapping.h in h8300, m32r and > m68k and leave !HAS_DMA as the obscure s390 case (this one already can't > use ATA because of !HAS_MMIO). If I'm reading the m68k code correctly, SUN3 is the one that doesn't have DMA. It is implemented on any m68k with a standard Motorola MMU. It might be possible to get the DMA code working on a sun3, but I doubt they ever have IDE hardware. Brad Boyer flar@allandria.com