On Saturday 04 February 2006 05:57, Mike Isely wrote: > On Sat, 4 Feb 2006, Helmut Toplitzer wrote: > > On Saturday 04 February 2006 02:08, Helmut Toplitzer wrote: > >> Hi! > >> > >> > >> Just in case .... > >> > >> Maybe Ingo Flaschberger's idea should be the default (tolerating > >> errors). > > > > But it doesn't work either... > > No surprise there. Covering a symptom does not solve the problem. > > > Maybe device should be reset. > > Resetting the device is a very disruptive operation. There's not even any > evidence that a reset of the device would help - especially if it isn't > the device that is the cause. I could try to code for something like > that, but again as I've said before, the device seems to be operating > reliably for pretty much everyone else which leads me to wonder if there > still isn't something unique to your configuration which is causing this > that has not yet been isolated. > > Don't get me wrong. I'm not trying to ignore you here. I'm just not > convinced that we have a real problem with the driver or the device in > general. >
Overall I just can't imagine why I hesitated so long to buy a new controller. At least I didn't got a headache as I would have if I had bought 5 beers instead. But wait ... ;-) -- My GNUpg fingerprint http://www.gnupg.org 4563 F4FB 0B7E 8698 53CD 00E9 E319 35BD 6A91 1656 ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
