Date: Mon, 26 Jan 2004 08:44:26 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: bpickles@sbs.com, BPICKLES@btconnect.com Cc: freebsd-arch@freebsd.org Subject: Re: Device Driver Problem, Embedded Development Message-ID: <20040126.084426.107520432.imp@bsdimp.com> In-Reply-To: <00c301c3e3eb$944845d0$1d02a8c0@sdlbase> References: <00c301c3e3eb$944845d0$1d02a8c0@sdlbase>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040126.084426.107520432.imp>