From owner-freebsd-questions Mon Mar 27 8:40:10 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id F2A1937BA10; Mon, 27 Mar 2000 08:38:02 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.calcaphon.com (henny.calcaphon.com [10.0.0.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id RAA78693; Mon, 27 Mar 2000 17:39:26 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Mon, 27 Mar 2000 17:32:24 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Jeff Fulton Cc: freebsd-questions@freebsd.org, Bill Paul Subject: RE: USB ethernet adapter from @Home In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm still curious about whether it should be possible to do this through > adds to usbd.conf No. The usbd daemon only decides on what to run in userland after the device has been attached to. What would be possible is store the information on what drivers to attach to what in a kernel loadable module that can be unloaded at any time. However, that approach opens up a whole can of worms: How to decide on which driver to use, how to make sure that the kernel does not fall over while the kernel module is not loaded (in between the 'kldunload' and 'kldload'), etc. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message