From owner-freebsd-new-bus Wed Oct 6 16:40:19 1999 Delivered-To: freebsd-new-bus@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id ADB811535D; Wed, 6 Oct 1999 16:40:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id AAA45749; Thu, 7 Oct 1999 00:42:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 7 Oct 1999 00:42:11 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: new-bus@freebsd.org, dfr@freebsd.org Subject: Re: Question on loading buses In-Reply-To: <199910062220.QAA07058@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Oct 1999, Warner Losh wrote: > > How can I load a bus? I have a simple bus that has device_identify > and device_probe methods. Neither of them seems to be called when I > kldload it. This is true when it is a isa driver or a nexus driver. > Am I doing something wrong? Currently all that happens when a driver is loaded is that the BUS_DRIVER_ADDED method of all instances of the parent bus is called. There is a generic implementation of BUS_DRIVER_ADDED which calls device_probe_and_attach() for any unmatched device instances but the parent probably doesn't have this in its method table. Probably bus_generic_driver_added() should call DEVICE_IDENTIFY for the new driver too. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message