From owner-freebsd-arch@FreeBSD.ORG  Mon Jan 26 07:48:10 2004
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 D004416A4CE
	for <freebsd-arch@freebsd.org>; Mon, 26 Jan 2004 07:48:10 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 86FA043DAA
	for <freebsd-arch@freebsd.org>; Mon, 26 Jan 2004 07:47:34 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0QFj3ET078327;
	Mon, 26 Jan 2004 08:45:04 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Mon, 26 Jan 2004 08:44:26 -0700 (MST)
Message-Id: <20040126.084426.107520432.imp@bsdimp.com>
To: bpickles@sbs.com, BPICKLES@btconnect.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <00c301c3e3eb$944845d0$1d02a8c0@sdlbase>
References: <00c301c3e3eb$944845d0$1d02a8c0@sdlbase>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-arch@freebsd.org
Subject: Re: Device Driver Problem, Embedded Development
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Mon, 26 Jan 2004 15:48:10 -0000

In message: <00c301c3e3eb$944845d0$1d02a8c0@sdlbase>
            "Bob Pickles" <BPICKLES@btconnect.com> writes:
: I have been trying to find the following functions:
: 
:     pci_mem_find()        Need explanation of parameters. Managed to work out the 
:                                   other pci_ functions...

This isn't a public function.  Don't use it.  In fact, I can't even
find it in the current sources.  I believe it was the old-style way to
map memory.

:     bus_space_map()    Need explanation of parameters to allow device memory map.

Chances are excellent you don't want to use this one either.

: This is all that I need to get the driver working with the user app.

bus_alloc_resource() is what I think you want to use.

Warner