On Sat, Feb 21, 2004 at 04:29:46PM -0500, Alan Stern wrote: > Greg and everyone else: > > Right now the routines in config.c bail out when they encounter almost any > kind of error in a device's configuration descriptors. That helps make > the system more reliable but also makes it difficult to track down > problems! It's embarrassing to tell a user that they have to boot 2.4 > just to see what /proc/bus/usb/devices or lsusb says about a buggy device.
How about just printing out better error messages when this happens? Like, "here is what we expected, and here is what this device reported. Please send this info to the linux-usb-devel mailing list..." That would be a good start, and probably quite easy to implement right now. > One thing that would be good, whether this change gets made or not, is to > remove all assumptions from drivers about the order in which interfaces > are stored (use usb_ifnum_to_if()) and the order in which altsettings are > stored (replace intf.act_altsetting with a pointer and create > usb_altnum_to_alt() analogous to usb_ifnum_to_if()). There are plenty of > drivers that will need to be fixed up. I'd be glad to take patches to fix up any drivers that still have this problem right now. thanks, greg k-h ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
