From owner-freebsd-current Tue Dec 15 20:45:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21025 for freebsd-current-outgoing; Tue, 15 Dec 1998 20:45:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21017 for ; Tue, 15 Dec 1998 20:45:08 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from sramhc.sra.co.jp (sramhc [133.137.20.31]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id NAA01713; Wed, 16 Dec 1998 13:44:37 +0900 (JST) Received: from sramhc.sra.co.jp (furuta@localhost [127.0.0.1]) by sramhc.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id NAA07797; Wed, 16 Dec 1998 13:44:51 +0900 (JST) Message-Id: <199812160444.NAA07797@sramhc.sra.co.jp> To: mike@smith.net.au Cc: y-nakaga@nwsl.mesh.ad.jp, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Your message of "Tue, 15 Dec 1998 20:17:07 -0800" References: <199812160417.UAA00907@dingo.cdrom.com> X-Mailer: Mew version 1.70 on Emacs 19.28.7 / Mule 2.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 16 Dec 1998 13:44:50 +0900 From: Atsushi Furuta Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In article <199812160417.UAA00907@dingo.cdrom.com>, Mike Smith writes: > If you haven't even looked at the issues involved in dynamic growth of > the newconfig-generated device and bus tree, then I'd have to strongly > suggest that you're wasting your effort right now. Of cource, *our* newconfig will be support dynamic growth of the device instance tree and device directed graph. Actually, I have changed from cfdata structure array to TAILQ. Please look at our repository... > Drivers required for the boot process need to be aggregated at either > build-time or load-time (console, root disk), and they can either be > statically or dynamically configured - static configuration is optional > and only required if the driver or its parend bus can't work things out > itself. I have a different opinion. As noted by Doug, current implementation of new-bus requires config(8) to specify ivars. It is not fair to say "newconfig is static, but new-bus is dynamic" without dynamic parameter specification. > The metainformation required to connect devices and busses is almost > entirely contained in the drivers themselves, rather than being > constructed at build-time by an extern configuration tool. This is > more or less mandatory if you want to be able to add arbitrary bus and > device code to a running system, and one of the major marks against > newconfig. Our newconfig will be able to specify such a metainformation not only at build-time, but also run-time. A key point is a counterpart in newconfig of devclass_add_driver(9) and device_add_child(9) of new-bus. It is not still implemented, but we eventually will implement. (may be soon) -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message