On Wed, 6 Dec 2006, Benjamin Herrenschmidt wrote: > The problem of the PCI module changing name should mostly be a non-issue > in most setups these days since udev etc... will still find it just > fine. (I didn't say on all setups... but most). > > I think it's just a bizarre approach inherited because of the way the > driver evolved that we have all the glues built-in.... > > I is more logical to split it. > > Now, it's your call. At this point, we need a solution, so what do you > want ? Either we keep everything in one module and hack the > module_init() to call the glues (which means ifdef's etc...) or we go to > the split modules approach. Whatever you want, we'll comply but we need > to do something for 2.6.20... :-)
Well, it's David's driver (officially now, thanks to a recent change to MAINTAINERS), and Greg would have to approve changes in the way the driver appears to userspace. Part from the userspace issue, the two approaches should work equally well. So I'll leave the decision up to them: Should ohci-hcd.ko be split up into ohci-hcd-core.ko plus things like ohci-pci.ko, ohci-omap.ko, etc.? Or should we continue to build a monolithic driver with #ifdef's to handle module initialization? Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
