On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote: > > The arm port has a USB host and client driver (or so I've been told, the > > client might be this one for all I know :) I've seen the host driver, > > and it will probably end up in the drivers/usb/ directory soon. Same > > thing goes for a embedded PPC USB host controller driver that is based > > off of usb-ohci.c, it too will end up in the drivers/usb directory soon. > > Hmm ... but why not keep architecture specific drivers > in the relevant arch/... subtree?
Because the changes made to the usb-ohci.c file are so minor, they should remain closly tied to the original usb-ohci.c file so as to pick up bug fixes in the main code. More on this when the developers doing this work have something to show us :) > Yes and no. Some changes are easier to do before > merges than after. > > At any rate, I'd hope that such things would be discussed > before integration. Not entirely clear to me that it shouldn't > be done on linux-usb-devel, though a more focust sublist > can often be big win. "linux-usb-devices"?? Though > as has been noted, the "USB On-The-Go" (peer-to-peer > USB) will affect both hosts and devices. I can create a linux-usb-devices list on linux-usb.org if Stuart doesn't mind. Might as well keep all of the relevant lists in the same place :) thanks, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
