From owner-freebsd-mobile Sun Apr 11 22:46:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 8F1D015175 for ; Sun, 11 Apr 1999 22:46:14 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id OAA11879; Mon, 12 Apr 1999 14:41:39 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: y-nakaga@nwsl.mesh.ad.jp Cc: mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Any success with CirrusLogic 6729/6730??? From: Tomoaki NISHIYAMA In-Reply-To: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> References: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990412144137C.tomoaki@moss.nibb.ac.jp> Date: Mon, 12 Apr 1999 14:41:37 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 29 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: NAKAGAWA Yoshihisa Subject: Re: Any success with CirrusLogic 6729/6730??? Date: Mon, 12 Apr 1999 10:53:44 +0900 Message-ID: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> y-nakaga> > I don't. You do. y-nakaga> y-nakaga> You are miss-understanding. Now, we are in agreement that an ISA PCIC is an ISA device and that a PCI PCIC is a PCI device. That is good enough and it's no use to discuss about who is responsible for the misunderstanding. We should go to the next major difference between new-bus and newconfig. As far as I understand, new-bus strategy is to put all the information of connection between bus and devices in individual device drivers, while newconfig strategy is to put the information in a file outside the kernel. Both are to put information of bus-device connection outside the kernel. The difference is where to put it. The reason why newconfig will put the information in a file is to make the user-configuration easier. The reason of new-bus to put the information in individual driver is to make it easier to load the module dynamic. Is this recognition right? I would like to hear from both sides. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message