Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Dec 1998 13:44:50 +0900
From:      Atsushi Furuta <furuta@sra.co.jp>
To:        mike@smith.net.au
Cc:        y-nakaga@nwsl.mesh.ad.jp, current@FreeBSD.ORG
Subject:   Re: PAO Integration? 
Message-ID:  <199812160444.NAA07797@sramhc.sra.co.jp>
In-Reply-To: Your message of "Tue, 15 Dec 1998 20:17:07 -0800"
References:  <199812160417.UAA00907@dingo.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>> In article <199812160417.UAA00907@dingo.cdrom.com>,
	Mike Smith <mike@smith.net.au> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812160444.NAA07797>