Am Mi, den 26.05.2004 schrieb Alan Stern um 22:39: > On Wed, 26 May 2004, Greg KH wrote: > > Now I really am not too eager to change that timeout value just for some > > obviously broken devices, but it might be worthwhile to make it a > > module_param() to allow users to tweak it if they so need to. > I won't try very hard to change your mind. However it is worth noting > that the long timeout will not affect systems with non-broken devices, > since they will stabilize in 100-200 ms. So there's not much penalty for > using the longer timeout -- it will cause systems to respond a bit slowly > when a broken device is plugged in, but that's better than not working at > all!
Absolutely! I also do not see any risk in increasing the timeout. Also 1500ms is still a very sane value. Even if a device should take almost that long to connect then a user will almost certainly not even recognise it. And all other well behaving devices are not changed! > Alan Stern CU nils faerber -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 -- ------------------------------------------------------- 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
