Date: Thu, 7 Oct 1999 01:31:39 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Warner Losh <imp@village.org> Cc: new-bus@FreeBSD.ORG, dfr@FreeBSD.ORG Subject: Re: Question on loading buses Message-ID: <Pine.BSF.4.10.9910070129570.327-100000@salmon.nlsystems.com> In-Reply-To: <199910070018.SAA07555@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 6 Oct 1999, Warner Losh wrote: > In message <Pine.BSF.4.10.9910070039460.571-100000@salmon.nlsystems.com> Doug Rabson writes: > : 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. > > You mean the following? The call should happen before the probe loop otherwise new devices created by the identify method won't be probed. Note that for the isa bus, we really need an isa_driver_added which can allocate pnp resources etc. after the identify creates them. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9910070129570.327-100000>