On Thu, Dec 12, 2002, Greg KH <[EMAIL PROTECTED]> wrote: > On Thu, Dec 05, 2002 at 08:56:20PM -0500, Johannes Erdfelt wrote: > > Right now, a user which has read privileges to usbdevfs devices can't get > > the driver bound to an interface via the usbdevfs interface. > > > > However, it is exposed via the devices file so I don't think this is on > > purpose. > > > > Would a patch like this be acceptable? (Untested, but it compiles) > > Looks ok to me at first glance. Does libusb work better with this > patch?
Yes. I had specifically been asked to add support for it to libusb for an application that Debian is working. However, it became obvious quickly that it wasn't as useful as we were hoping since write privileges to the device is needed right now. > And there's no problems with anyone reading proc_disconnectsignal(), > right? I looked at it and I think it's safe, however, it's completely unrelated to the original goal of the patch. I can make a new patch which is a bit more conservative until I (and hopefully someone else) can look at the proc_disconnectsignal change as well. JE ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
