From owner-freebsd-arch@FreeBSD.ORG  Fri Jun 27 15:30:59 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 8426F37B401
	for <freebsd-arch@freebsd.org>; Fri, 27 Jun 2003 15:30:59 -0700 (PDT)
Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A152644001
	for <freebsd-arch@freebsd.org>; Fri, 27 Jun 2003 15:30:58 -0700 (PDT)
	(envelope-from gibbs@scsiguy.com)
Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11])
	by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h5RMU7822962;
	Fri, 27 Jun 2003 15:30:07 -0700
Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70])
	by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id PAA02455;
	Fri, 27 Jun 2003 15:30:57 -0700 (PDT)
Date: Fri, 27 Jun 2003 16:32:07 -0600
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>,
	Scott Long <scott_long@btc.adaptec.com>
Message-ID: <721230000.1056753126@aslan.btc.adaptec.com>
In-Reply-To: <16124.48285.343025.428957@grasshopper.cs.duke.edu>
References: <3EF3C12F.9060303@btc.adaptec.com>
	<16124.39930.142492.356163@grasshopper.cs.duke.edu>
	<3EFC9F2D.6020908@btc.adaptec.com>
	<16124.43999.333761.397624@grasshopper.cs.duke.edu>
	<3EFCAC7A.6060305@btc.adaptec.com>
	<16124.45051.919899.414795@grasshopper.cs.duke.edu>
	<3EFCB178.9030207@btc.adaptec.com>
	<16124.46454.595892.860118@grasshopper.cs.duke.edu>
	<3EFCB725.4060902@btc.adaptec.com>
	<16124.48285.343025.428957@grasshopper.cs.duke.edu>
X-Mailer: Mulberry/3.0.3 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
cc: freebsd-arch@freebsd.org
Subject: Re: API change for bus_dma
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: "Justin T. Gibbs" <gibbs@scsiguy.com>
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2003 22:30:59 -0000

>  > As I understand it, it is possible to set the pycho bridge to use
>  > a coherent address range, but FreeBSD doesn't take advantage of that
>  > yet.
>  > 
> 
> Yes, that's what solaris does..

We added BUS_DMA_COHERENT to the API just before shipping 5.1.  It
is only a "hint", so if you need to verify that the implementation
was able to give you coherent memory, we should add an API to allow
you to know.  Of course, the Sparc bus dma implementation doesn't honor
the flag yet, but I'm sure that will change shortly.

--
Justin