From owner-freebsd-arch@FreeBSD.ORG Tue Jun 17 11:06:24 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24CD737B407; Tue, 17 Jun 2003 11:06:24 -0700 (PDT) Received: from mail.cyberonic.com (mail.cyberonic.com [4.17.179.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 213DC43F75; Tue, 17 Jun 2003 11:06:21 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (node-40244c0a.sfo.onnet.us.uu.net [64.36.76.10]) by mail.cyberonic.com (8.12.8/8.12.5) with ESMTP id h5HIW6Mo015646; Tue, 17 Jun 2003 14:32:07 -0400 Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.9/8.11.6) id h5HI6iIq033086; Tue, 17 Jun 2003 11:06:44 -0700 (PDT) (envelope-from jmg) Date: Tue, 17 Jun 2003 11:06:44 -0700 From: John-Mark Gurney To: Maxime Henrion Message-ID: <20030617180644.GL73854@funkthat.com> Mail-Followup-To: Maxime Henrion , Harti Brandt , arch@freebsd.org References: <20030617124004.Y77677@beagle.fokus.fraunhofer.de> <20030617115330.GS21011@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030617115330.GS21011@elvis.mu.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: arch@freebsd.org Subject: Re: busdma sync problem X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 18:06:24 -0000 Maxime Henrion wrote this message on Tue, Jun 17, 2003 at 13:53 +0200: > whole map. However, I believe it would be more beneficial at this point > in time to try to make our busdma API as close as NetBSD's one as > possible. I bet we'll end up using more macros, as the NetBSD folks do Actually, right now, our bus/device interface is so far away that it'll take a lot of work. NetBSD shares bus_tag's between DMA and bus_space, so w/ FreeBSD, you already have to add a bus dma tag for each bus dmamap that you use in the driver. The dmamap is not an opaque type and you do not require callbacks to get the address for each segment. Sure you can start with some small things, but I don't think these are a big deal, (heck it might even confuse some people), till the rest of the bus_dma interface has been "merged". -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."