[quoted lines by Greg KH on 2007/08/01 at 17:05 -0700] >There is a kernel configuration option to retain this if you really need >it.
In this case, that's not really the issue. We maintain brltty, which is used by blind users who use braille displays. To them, their braille displays are their screens. They're typically just regular users who may not have the experience it takes to rebuild their kernels. We must implement our code in a way that just works for them so having to enable a kernel parameter isn't the way to go here. >Right now the information is already availble in sysfs in a >different location (/sys/bus/usb/devices) so having this is redundant. Is there a way to map usbfs bus and device numbers to the device names in that directory? If not, how should we go from usbfs to sysfs? Is it really necessary to iterate ovder all those sysfs devices just to find the usbfs device we already have? It really was nice to be able to map directly. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. http://FamilyRadio.com/ | http://Mielke.cc/bible/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
