Date: Sat, 20 May 2006 13:39:08 +0800 From: "william wallace" <avalonwallace@gmail.com> To: "Warner Losh" <imp@bsdimp.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: misc questions about the device&driver arch Message-ID: <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> In-Reply-To: <20060519.232002.71106210.imp@bsdimp.com> References: <87ab37ab0511032030o134b9316j83295dd303e4e44b@mail.gmail.com> <87ab37ab0605192015h363ef74aw23dcc2d97721dea9@mail.gmail.com> <20060519.232002.71106210.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
comparing the method array of pci_pci and cardbusbridge: what losts in pci bridge but exist in cardbusbridge: 1 card interface 2 power interface 3 some functions : 3ain bus interface (bus_driver_added, cbb_driver_added), (bus_child_detached, cbb_child_detached), (bus_child_present, cbb_child_present), 3b in device interface (device_detach, cbb_detach), what exists in pci bridge but losts in cardbusbridge: (pcib_route_interrupt, pcib_route_interrupt), not only that ,functions r very different eventhough they realize the same interface function template wooo，so long to go to hotplug pci On 5/20/06, Warner Losh <imp@bsdimp.com> wrote: > Busses create devices to represent hardware in the system. The bus > then causes these devices to be probed and attached. This latter > usage is for those cases. As drivers are loaded these devices are > offered to the new (and old) drivers in the system. > > FreeBSD inherently dynamic in its device system. The hardest part of > adding hotplug support is programming the bridge. Adding new devices > to the tree is easy, but knowing when to add them is hard since you > have to write a bridge driver... > > Warner > -- we who r about to die,salute u!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3>