Date: Wed, 16 Dec 1998 11:50:58 +0900 From: NAKAGAWA Yoshihisa <y-nakaga@nwsl.mesh.ad.jp> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG Subject: Re: PAO Integration? Message-ID: <199812160250.LAA03052@chandra.eatell.msr.prug.or.jp> In-Reply-To: Your message of "Tue, 15 Dec 1998 04:31:37 PST." <199812151231.EAA05213@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> config(8) does two things; it builds static tables of configuration > data, and it arranges for code aggregation into a kernel object. newconfig" is not only config(8), but also include bus and device configuration code. See: sys/kern/subr_autoconf.c (in "newconfig", it it much better.) Now, "newconfig" support static-linked kernel only, but it is first step. On near future, we support UserConfig, and next target is dynamic loadable module. These configuration, we support "newconfig" integrated. > > On "new-bus", How to handle boot device like console, fd, wd, ... ? > > I can't make sense of this question; could you expand a little? I think, some case needs statically-configuration. So, using boot-time divices, I think that they are statically-configurated. I want to know if new-bus using another way. Mike, new-bus is good; but "newconfig" is also good, I think. Until now, same purpose drivers stand side by side in FreeBSD. (example, Voxware and Luigi's new audio driver, BSD ATM and HARP, ...) "new-bus" and "newconfig", I think same relation. Choose by users. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org 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?199812160250.LAA03052>