Greg KH wrote: > It will be kept and working as usual in the kernel.org kernel. > > However, some distros might not be mounting it by default anymore, and > if they do that, they are shipping a modified libusb that handles > everything properly for you by using the correct device nodes. For > example, SuSE 10.0 is like this. > > If you have a distro specific issue because of them not mounting usbfs > by default, please take it up with them, there's not much we can do from > the kernel itself. > > Hope this helps,
thanks, it does. the kernel passes /proc/bus/usb/xxx/yyy as DEVICE argument in hotplug events, I guess it does the same with the daemon based communication? will udev or hald take care of replacing that string with the pathname of the new device file in /dev/? if we still get a DEVICE for new usb hardware plugged in and can open() it like we used to, and use the same ioctl the biggest hurdle is solved. the other problem we have is cold plugging: on bootup we need to create our own status file, and then generate cold plugging events for all hardware already plugged in. i.e. start programs and pass a DEVICE string. we use libusb for scanning all devices, but need to create the device string ourself, as libusb has no function to tell us. because of that we have a hard coded "/proc/bus/usb/%03d/%03d" in our code. If distributions don't mount usbfs per default, they change that code - I hope - and we should be fine. Regards, Andreas ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
