Date: Sun, 30 Mar 1997 13:21:09 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Doug Rabson <dfr@nlsystems.com> Cc: current@freebsd.org Subject: Re: A new Kernel Module System Message-ID: <20519.859756869@time.cdrom.com> In-Reply-To: Your message of "Sun, 30 Mar 1997 12:35:45 %2B0100." <Pine.BSF.3.95q.970330115909.6939A-100000@kipper.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> For adding devices dynamically, a new system call would create an > isa_device structure and fill it with the new device's config data (io, > irq, flags etc.) The new device will then match against the installed > drivers by name as for static devices. The commands used might be > something like: > > # Add a new device using ed driver > isaconf -a ed0 port=0x280 irq=5 iomem=0xd8000 flags=4 > # Load the ed driver to activate all ed* instances > modload /lkm/devs/isa/ed.so Ah, OK, this is the bit I missed. So you'd use this to load drivers that the kernel had never seen before, e.g. say I get a floppy from ABC Systems along with their new network interface card which none of us have ever even heard of before, and when I say: mcopy a:abc_foonic.so /lkm/devs/isa isaconf -a foo0 port=0x320 irq=11 iomem=0xd0000 modload /lkm/devs/isa/foo0.so It all does the right stuff? What if it's a PCI or EISA card, do I just do the modload and expect it to DTRT? Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20519.859756869>