On Tue, Oct 08, 2002 at 02:00:57PM -0700, David Brownell wrote: > > I think device speed is still unavailable through KFS,
Good catch, I'll go add that. > and I suspect the extra audio descriptor bytes aren't exposed, but > other than that the read-only access modes are about equivalent. That should go into the audio driver, not the usb core. > But USBFS lets you interact with the device, and every user mode driver > (or configuration tool) relies on that. Many of them hook up through > hotplug. KFS doesn't; which is why the agents will continue to need > the USBFS path. I want to remove the fact that usbfs is being used by the hotplug scripts. I don't care about any userspace drivers or configuration scripts, they can determine the usbfs location from the driverfs/kfs device already. > There's also the "coldplug" situation. KFS _could_ remember which > devices didn't have hotplug events issued (a device state flag) and > rescan its tree to issue them, after the kernel's come up enough that > /sbin/hotplug can safely be called. Only solving that issue lets us > completely get rid of "usbmodules". No, kfs isn't going to do a "coldplug" store and replay thing. What is going to happen is /sbin/hotplug will be present early in the boot due to initramfs, so the proper modules will already be loaded. If userspace wants to walk the driverfs/kfs tree when init starts up, that's up to it. And yes, I really want to get rid of usbmodules too :) > >Also, any reason to keep the DEVFS variable? It's wrongly named, and > >doesn't look like anyone uses it. > > Not any longer. But update the docs (on the hotplug website). Will do. thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
