From owner-freebsd-mobile Mon Apr 12 3:15:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 00659150B6 for ; Mon, 12 Apr 1999 03:15:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA42949; Mon, 12 Apr 1999 11:00:45 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 11:00:45 +0100 (BST) From: Doug Rabson To: Tomoaki NISHIYAMA Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@freebsd.org Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <19990412144137C.tomoaki@moss.nibb.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, Tomoaki NISHIYAMA wrote: > 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. This is right. The reason device attachment points are not specified in the config file is that I don't think the user should need to care how the hardware in their machine works in order to get FreeBSD working. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message