Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Mar 1997 10:49:05 -0700
From:      Warner Losh <imp@village.org>
To:        Doug Rabson <dfr@nlsystems.com>
Cc:        "Jordan K. Hubbard" <jkh@time.cdrom.com>, current@freebsd.org
Subject:   Re: A new Kernel Module System 
Message-ID:  <E0wBlCc-0006sH-00@rover.village.org>
In-Reply-To: Your message of "Mon, 31 Mar 1997 11:15:33 %2B0100." <Pine.BSF.3.95q.970331111048.534H-100000@kipper.nlsystems.com> 
References:  <Pine.BSF.3.95q.970331111048.534H-100000@kipper.nlsystems.com>  

next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.3.95q.970331111048.534H-100000@kipper.nlsystems.com> Doug Rabson writes:
: 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....

That is I'd like to be able to boot a generic thing, and have it
preserve my deltas to the "settings" of the device drivers across
upgrades.  It is often nice to have one GENERIC kernel that gets
pushed out to n sites who's only differences are the IRQs and I/O
addresses of some of the ethernet cards, etc.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0wBlCc-0006sH-00>