From owner-freebsd-current Mon Apr 19 2: 8:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 2CDF914FE3 for ; Mon, 19 Apr 1999 02:08:38 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id RAA01297; Mon, 19 Apr 1999 17:57:16 +0900 (JST) Message-Id: <199904190857.RAA01297@shidahara1.planet.sci.kobe-u.ac.jp> To: Doug Rabson , freebsd-current@freebsd.org Dcc: Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 09:33:27 +0100" References: Date: Mon, 19 Apr 1999 17:57:16 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Do ug Rabson wrote: >On Mon, 19 Apr 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: >> Simple Question. >> If there were 'Closed'-Host-Controller-Interface with object-only driver, >> Can the vendor make the Host controller recognized without changing >> usb.c code? >> >> #That's what frustrated me while writing driver for smbus controller. > >It really depends on the nature of the bus. For plug-and-play style busses >such as USB and PCI, the controller can decide what devices exist without >the help of drivers and can then uniquely match them with the right >driver. This trivially allows drivers to be added after the system is >running. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message