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 <[EMAIL PROTECTED]> 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!
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
