From owner-freebsd-current Sun Mar 30 13:21:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA13502 for current-outgoing; Sun, 30 Mar 1997 13:21:21 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13493 for ; Sun, 30 Mar 1997 13:21:18 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id NAA20523; Sun, 30 Mar 1997 13:21:09 -0800 (PST) To: Doug Rabson cc: current@freebsd.org Subject: Re: A new Kernel Module System In-reply-to: Your message of "Sun, 30 Mar 1997 12:35:45 +0100." Date: Sun, 30 Mar 1997 13:21:09 -0800 Message-ID: <20519.859756869@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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