On Wed, Mar 20, 2002 at 11:17:25PM +0100, Oliver Neukum wrote: > > > What ones? I can't think of any right off the top of my head. > > ioctls for getting complex information.
read() works fine for getting complex information too :) > > > Folk would benefit from being able to bind/unbind drivers from > > > interfaces (viz that recent VMWare note, and there are other cases > > > too). > > > > Agreed. The pencam userspace program has this problem right now with > > the video kernel driver being bound to the device. I'd love a solution > > for that right now, so much that I'd be willing to add a new ioctl :) > > > > > Taking a new approach to usbfs might be productive, but that > > > might make it look more like a driverfs add-on ... :) > > > > Heh, the idea is the same (no ioctls, read and write different files), > > but it would be separate from the driverfs tree probably, as it doesn't > > pertain to the main driverfs issue. > > > > See pcihpfs in the kernel right now for an idea of what I am thinking > > of. > > This does look like yet another filesystem. It is another filesystem. If you look in /proc/filesystems, you will see lots of them. They are multiplying! And with libfs in the 2.5 kernel now, they are easier than ever to write. > We need some centralised point for doing > device configuration. That's what userspace tools are for :) thanks, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
