From owner-newconfig-jp@jp.freebsd.org  Wed Jan  6 02:44:44 1999
Received: by jaz.jp.freebsd.org (8.9.1+3.1W/8.7.3) id CAA29484;
	Wed, 6 Jan 1999 02:44:44 +0900 (JST)
	(envelope-from owner-newconfig-jp@jp.FreeBSD.org)
Received: from shidahara1.planet.kobe-u.ac.jp (root@shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by jaz.jp.freebsd.org (8.9.1+3.1W/8.7.3) with ESMTP id CAA29479
	for <newconfig-jp@jp.freebsd.org>; Wed, 6 Jan 1999 02:44:43 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
From: takawata@shidahara1.planet.sci.kobe-u.ac.jp
Received: from libr.scitec.kobe-u.ac.jp (cs22245.ppp.infoweb.ne.jp [202.219.171.61])
	by shidahara1.planet.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id CAA13280
	for <newconfig-jp@jp.freebsd.org>; Wed, 6 Jan 1999 02:35:59 +0900 (JST)
Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id CAA01918 for <newconfig-jp@jp.freebsd.org>; Wed, 6 Jan 1999 02:43:58 +0900 (JST)
Message-Id: <199901051743.CAA01918@libr.scitec.kobe-u.ac.jp>
To: newconfig-jp@jp.freebsd.org
In-reply-to: Your message of "Wed, 06 Jan 1999 00:22:02 JST."
             <19990106002202B.furuta@sra.co.jp> 
Date: Wed, 06 Jan 1999 02:43:57 +0900
Reply-To: newconfig-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+981115
X-Sequence: newconfig-jp 820
Subject: [newconfig-jp 820] Re: Can I use bus_*_t ??? 
Errors-To: owner-newconfig-jp@jp.freebsd.org
Sender: owner-newconfig-jp@jp.freebsd.org
X-Originator: takawata@shidahara1.planet.sci.kobe-u.ac.jp

In message <19990106002202B.furuta@sra.co.jp>, Atsushi Furuta $B$5$s$$$o$/(B:
>  sys/i386/include/bus.h $B$GDj5A$5$l$F$$$k$b$N$O<+M3$K;H$C$FNI$$!"$G$$(B
>$B$$$N$G$O$J$$$+$H;W$$$^$9!#$$$1$J$$M}M3$O$A$g$C$H;W$$$D$1$^$;$s$G$7$?!#(B

$B$J$s$+!"(Bhackers$B$+$I$C$+$G:G6a$=$l$,OCBj$K$J$C$F$F!"%j%=!<%93d$jEv$F4X?t$,(B
FreeBSD$B$K$J$$$H$+2?$H$+8@$C$F$A$g$C$H$7$?5DO@$K$J$C$F$?$h$&$J5$$,$7$^$9$,!#(B
$B$G!":#F|8+$F$k$H!"(BDoug Robson$B;a$,(BNetBSD$B$N$=$NJU$N%^%K%e%"%k$J$$$+$H$+(B
$B8@$C$F$?$h$&$J!#(B
$B!t$J$s$+$3$l$r;H$&J}8~$K$O$$$+$J$$$H8@$C$F$k?M$,$$$F!";H$$$^$/$C$F$k(B
$B!t;d$O$A$HNd4@$+$-$J$,$i$-$$$F$?$N$G$7$?!#(B


$BEOJUB:5*(B
$B?@8MBg3XBg3X1!<+A32J3X8&5f2J(BD1$B>pJs%a%G%#%"2J3X@l96!#(B
<a href="http://www.planet.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 
$B$3$s$J46$8(B

Subject: Re: bus_space_foo and bus_dmamap_foo 

I think that this is the right approach.  The interface for PCI busses
should have methods to manage the various device resources and these will
be able to provide bus_space handles as necessary.  The resources should
not need to be mapped directly by the pci driver.  I'm currently
prototyping the new PCI interface (or I will be as soon as I can get that
wretched sysinstall program working properly on the alpha) and I'll add
something like this.

Are there any manpages for bus_space and bus_dma in NetBSD which we can
take?

--
Doug Rabson                             Mail:  dfr@nlsystems.com
