From owner-freebsd-hackers Mon Aug 9 22:18: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 1CF9E14A12 for ; Mon, 9 Aug 1999 22:17:58 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id OAA09396; Tue, 10 Aug 1999 14:47:20 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199908100517.OAA09396@gizmo.internode.com.au> Subject: Re: freebsd-hackers-digest V4 #576 To: ognir@humboldt1.com (Joe Groff) Date: Tue, 10 Aug 1999 14:47:20 +0930 (CST) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Joe Groff" at Aug 9, 99 10:14:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking wrote: > The recent chatter about allowing kldload to give modules arguments is very > interesting, as it would allow one to specify port addresses and the like. Would it be useful to be able to be able to do something like this: kldload -t kernel_config /sys/i386/conf/YOURKERNELNAME ... and have drivers consult the information they find in there for config hints? If newbus knew how to reconstruct config_devtab at runtime by parsing a "kernel_config" module's "device" and "controller" lines, we'd get dynamic runtime reconfiguration for free. It could even defer the initial construction of config_devtab until boot-time if you used "options INCLUDE_CONFIG_FILE" to provide default configuration data... - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message