From owner-freebsd-hackers Sun Mar 28 9:56: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7481B14C48 for ; Sun, 28 Mar 1999 09:55:56 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA14621; Sun, 28 Mar 1999 12:55:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA56973; Sun, 28 Mar 1999 12:55:27 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 28 Mar 1999 12:55:26 -0500 (EST) To: Doug Rabson Cc: freebsd-hackers@freebsd.org Subject: Re: kld questions In-Reply-To: References: <14077.30470.231888.128618@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14078.27843.489740.844029@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson writes: > > The current pci code has some remnants of old LKM support but I don't > think it includes anything functional. The new pci code which I am slowly > working on will support loadable drivers (that is the whole point really). > This nearly works now with one missing piece (the system needs to re-probe > unrecognised devices after a new driver is loaded). Now I have a reason other than esthetics to look forward to the new PCI code. ;-) Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message