thank u,sir :) i have been reading ur pccbb code for a long time . really elegant.here I think my ignorace is partly because the lack of reading to the doc about the generic device architecture .but frankly ,i still haven't fount the newbus-draft :( mention to pccbb ,i wonder the reason why pccard driver is so different from the cardbus and still attach to the same pci carbus bridge level . thanks again sir :)
On 12/2/05, M. Warner Losh <[EMAIL PROTECTED]> wrote: > In message: <[EMAIL PROTECTED]> > "M. Warner Losh" <[EMAIL PROTECTED]> writes: > : In message: <[EMAIL PROTECTED]> > : kylin <[EMAIL PROTECTED]> writes: > : : sir : > : : I am now working on the pci e hotplug of freebsd ,and reading code > : : of the relative part in linux. > : : i have never touch the field of USB . > : : now i wonder the mechanism of USB hotplug and the scsi hotplug . > : : in linux and my working on freebsd ,there r specail mechanism to > : : waiting for the hotplug event ,and the IRQ and MEM IO resource > : : allocation is complex . > : : i am fresh to the USB and the even complex SCSI driver arch , could u > : : give me some advise ? > : > : All FreeBSD devices use devd. Unlike Linux, FreeBSD's generic device > : architecture means that all busses automatically support hot plugging > : hooks. > > I'll add that each bus just needs to implement what it needs to for > the device's arrival and departure. See pccbb for one example. The > allocation algorithms aren't that complex or difficult because FreeBSD > dynamically allocates all the non-wired resources. > > Warner > -- we who r about to die,salute u! _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
