On Sat, May 29, 2004 at 03:49:24PM -0400, Alan Stern wrote: > Granted that's so, it doesn't mean we need to use ->serialize. And if we > do, the parts of usbcore that could send messages to ep0 (probably just > the usbfs and sysfs routines) will have to be changed to lock the device.
I don't know if this is similar, but I had problems with /proc/bus/usb/devices causing errors on active devices on 2.4. I'm using a device that's being polled with a control message at about 100Hz, and the usb_string() calls made by usb_dump_device_strings() aren't serializing with the ones being made by the device's drivers, resulting in ENXIO errors from uhci_submit_urb. My solution was to disable those string queries for that particular device; I wish there was a way to get all of that information without sending messages to devices. (Just serializing it wouldn't be a good solution for me, since I don't want to send unnecessary messages to the other device--it might interrupt the flow of 100Hz polls.) Ultimately what I'm doing is mapping USB pen drives to /etc/fstab mountpoints, USB hub/port/level numbers, and getting fast insert/removal notification via poll(). I'm getting this by parsing lsusb -v, /proc/bus/usb/devices, /etc/fstab and /proc/scsi/usb-storage-#/#; most of the mapping between files is via the serial number. It's horribly roundabout ... -- Glenn Maynard ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
