Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262734AbVCPSsr (ORCPT ); Wed, 16 Mar 2005 13:48:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262746AbVCPSrc (ORCPT ); Wed, 16 Mar 2005 13:47:32 -0500 Received: from omx2-ext.sgi.com ([192.48.171.19]:8121 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S262751AbVCPSp2 (ORCPT ); Wed, 16 Mar 2005 13:45:28 -0500 From: Jesse Barnes To: Keir Fraser Subject: Re: [PATCH] Xen/i386 cleanups - AGP bus/phys cleanups Date: Wed, 16 Mar 2005 10:42:02 -0800 User-Agent: KMail/1.7.2 Cc: Christoph Hellwig , akpm@osdl.org, Ian.Pratt@cl.cam.ac.uk, linux-kernel@vger.kernel.org, Rik van Riel , kurt@garloff.de, Christian.Limpach@cl.cam.ac.uk References: <20050316181042.GA26788@infradead.org> <521a4568db3e955cb245d10aaba2d3ce@cl.cam.ac.uk> In-Reply-To: <521a4568db3e955cb245d10aaba2d3ce@cl.cam.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503161042.03886.jbarnes@engr.sgi.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1403 Lines: 30 On Wednesday, March 16, 2005 10:35 am, Keir Fraser wrote: > On 16 Mar 2005, at 18:10, Christoph Hellwig wrote: > > On Wed, Mar 16, 2005 at 10:01:07AM -0500, Rik van Riel wrote: > >> In the case of AGP, the AGPGART effectively _is_ the > >> IOMMU. Calculating the addresses right for programming > >> the AGPGART is probably worth fixing. > > > > Well, it's a half-assed one. And some systems have a real one. > > > > But the real problem is that virt_to_bus doesn't exist at all > > on architectures like ppc64, and this patch touches files like > > generic.c and backend.c that aren't PC-specific. So you > > effectively break agp support for them. > > The AGP driver is only configurable for ppc32, alpha, x86, x86_64 and > ia64, all of which have virt_to_bus. Yeah, but that doesn't mean it makes sense on all those platforms. The biggest problem with virt_to_bus (well, depending on who you talk to) is that it can't handle systems where the address translation must be done differently depending on *which* bus we're getting a bus address for. Not sure what makes sense in this case though... is the DMA mapping interface appropriate? Jesse - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/