Date: Thu, 13 May 1999 08:28:28 +0900 (JST) From: Noriyuki Soda <soda@sra.co.jp> To: Mike Smith <mike@smith.net.au> Cc: Noriyuki Soda <soda@sra.co.jp>, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c Message-ID: <199905122328.IAA01375@srapc342.sra.co.jp> In-Reply-To: <199905122209.PAA01534@dingo.cdrom.com> References: <199905120901.SAA04493@srapc288.sra.co.jp> <199905122209.PAA01534@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Wed, 12 May 1999 15:09:05 -0700, Mike Smith <mike@smith.net.au> said: > It would appear that you don't understand the problem, as no > configuration technique can telepathically determine in advance which > new drivers you are going to load. Apparently you misunderstand newconfig. :-) There is compiled format of "files" file which path is known by kernel. >> - newconfig can cope with both static configuration and dynamic >> configuration. new-bus can handle dynamic configuration only. > This is actually a major defect in the newconfig design; if the kernel > doesn't already know about a device when it is built, it can never > support it. Apparently you misunderstand newconfig, too. :-) See above. >> The way on new-bus will cause compatibility problem when >> OS is upgraded, because the implementation (filename) may >> be changed between versions and versions. > This is a transient implementation issue, the obsolecesnce of which is > already manifest in the plans that have been laid for a device > identifier to module to file lookup with the translation data _outside_ > the kernel. In other words, that is not compatible with the BSD way where FreeBSD and BSDI and NetBSD and OpenBSD already probed. It is actually true that FreeBSD becomes Linux. -- soda 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?199905122328.IAA01375>