Date: Tue, 1 Apr 1997 14:25:58 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Terry Lambert <terry@lambert.org> Cc: Warner Losh <imp@village.org>, jkh@time.cdrom.com, current@freebsd.org Subject: Re: A new Kernel Module System Message-ID: <Pine.BSF.3.95q.970401142211.305E-100000@kipper.nlsystems.com> In-Reply-To: <199703311849.LAA09880@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Mar 1997, Terry Lambert wrote: > > : Almost. You would load /lkm/devs/isa/foo.so. The driver object does not > > : need an instance number since the same driver could support many different > > : instances: > > : > > : isaconf -a foo0 port=320 irq=10 iomem=0xd0000 > > : isaconf -a foo1 port=330 irq=11 iomem=0xd8000 > > : isaconf -a foo2 port=340 irq=12 iomem=0xe0000 > > : modload /lkm/devs/isa/foo.so > > > > That would be way cool. I'd especially like to be able to do this > > with the GENERIC kernel. Right now there is no way to do this, short > > of booting -c. When you install a new kernel on a machine at a remote > > office and thinkn that you are set because the old kernel was generic > > too and do a reboot, only to find out that it really wasn't generic > > GENERIC.... > > It seems to me that either the isaconf and the modload order is > inverted, or that the kernel should be demand loading the driver > for the isaconf case if the driver were not already present (the > loading done by the *kernel*, not the *isaconf*)... in which case > there should not be a modload at all. Actually, the modload could happen at any time. You could load the driver and attach instances to it after, or you could add device instances first and then load the driver, which would automatically go through the list of unbound instances and attach them to the new driver. It would be possible for isaconf(8) or the kernel to automatically load the driver but this isn't necessary for the purposes of the example. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970401142211.305E-100000>