On 1/1/09, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 1 Jan 2009, Alon Bar-Lev wrote: > > > Found it!!!! > > > > It woks within usbfs (/proc/bus/usb/999/999) and not within udev > > (/dev/bus/usb/999/999). > > > > Alan, I can see that in 2.6.28 at commit [1] you tried to make the > > kernel behave correctly for /dev/bus/usb devices. > > > > But apparently it does not work for me, can you please instruct me how > > to use your modification so that systems with udev and without usbfs > > will be able to detect device disconnect? > > > As I said earlier, both ways work on my system. I have no idea what's > going wrong on your machine. Please try to compile a kernel without CONFIG_USB_DEVICEFS and see if the program works for you? The device at /dev/bus/usb will be available but won't accept the disconnect signals. > However, you should realize that every Linux system that supports usb > has usbfs. All you need to do is mount /proc/bus/usb if it isn't > already mounted. No... you can compile a kernel without CONFIG_USB_DEVICEFS and work find with any USB devices using the udev device created at /dev/bus/usb. All is working except of the disconnect signal. I am working without the usbfs mounted for a very long time without any issue... This is the first difference I detected, while trying to improve openct. Thank you, Alon. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
