Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Apr 1999 19:28:48 +0800
From:      Peter Wemm <peter@netplex.com.au>
To:        Doug Rabson <dfr@nlsystems.com>
Cc:        Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>, freebsd-current@freebsd.org
Subject:   Re: newbus and modem(s) 
Message-ID:  <19990419112851.17D6F1F5E@spinner.netplex.com.au>
In-Reply-To: Your message of "Mon, 19 Apr 1999 10:27:36 %2B0100." <Pine.BSF.4.05.9904191021270.85882-100000@herring.nlsystems.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote:
> On Mon, 19 Apr 1999, Takanori Watanabe wrote:
> 
> > In message <Pine.BSF.4.05.9904190929070.85882-100000@herring.nlsystems.com>
    , 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?
> 
> I don't think I understand. The DRIVER_MODULE declaration goes in the
> downstream driver, not the upstream bus. The bus doesn't need any
> knowledge of what drivers might be attached to it.

Well, what about the i386 nexus?  It specifically creates connection points
for apm, npx, eisa, isa, and pci as children.

However, pci devices don't do this to attach to their parent.  I am
obviously missing something. :-)

Cheers,
-Peter




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990419112851.17D6F1F5E>