From owner-freebsd-mobile Mon Apr 12 3:20:36 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 700CF15319 for ; Mon, 12 Apr 1999 03:20:32 -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 LAA42969; Mon, 12 Apr 1999 11:03:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 11:03:44 +0100 (BST) From: Doug Rabson To: NAKAGAWA Yoshihisa Cc: Mike Smith , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@freebsd.org Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904120754.QAA09135@chandra.eatell.msr.prug.or.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, NAKAGAWA Yoshihisa wrote: > > This is specifically why we still use hint information from the > > configuration file. The goal, however, is to get away from compiling > > that hint information into the kernel. > > # newconfig members' (me too) opinion below: > > Our newconfig is better than yours new-bus in this point. > Newconfig supports both dynamic configration and static configuration, > so newconfig can do what new-bus can do, and also newconfig can > support particular configurations which new-bus can't. > (e.g. specially tuned kernel for particular purpose.) I would be interested in a specific example here. I don't understand what kind of tuning you are suggesting. > > Also, in newconfig case, we don't have to load the code which support > an ISA PCIC, if only an PCI PCIC code is needed, because we split an > PCIC driver to three part, an ISA attachment, an PCI attachment, and > bus independent shared part. In new-bus case, we suppose that you > have to load both the code which supports an PCI PCIC and the code > which supports an ISA PCIC. So, newconfig kernel is smaller and > faster to boot and more dynamic than new-bus. > Especially because new-bus doesn't have the feature to treat the > shared part of the device driver like this. This is not correct. A driver can be trivially split up into attachment points and implementations. The interface definition system can actually make this easier (IMHO of course). The mcclock driver in FreeBSD/alpha (derived from the NetBSD driver) does this. -- 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